Add windows property to new infrastructure by derickr · Pull Request #6 · derickr/php-infrastructure

derickr · 2026-03-19T17:13:44Z

The idea is that this replaces the current windows.php.net server, with redirects for all original content to the new location on either downloads.php.net or their integrated location on www.php.net

It's possible that I am missing better redirects for common links, so please let me know if I am missing any important ones.

/cc @shivammathur @jrfnl

jrfnl · 2026-03-19T17:28:01Z

@derickr Thanks for the ping.

While redirecting makes sense, there are a couple of things I'm a little concerned about:

The info which is in the left sidebar of the windows.php.net page, in particular the information about Visual Studio. I remember when I first installed PHP for Windows myself (without a WAMP installer), that info saved my bacon.
Access to historical versions as https://www.php.net/releases/ looks to only contain the Linux versions.

I'd also be interested to know how to get to QA releases for Windows. Looks like this is via https://www.php.net/pre-release-builds.php ? If so, where can I submit a PR to make that page a little more scannable ?

I'm also not so sure about that "I want to use PHP for" dropdown - is it just me or does nothing change when you toggle between "Web development" and "CLI/library dev" ?

jrfnl · 2026-03-19T17:30:31Z

roles/properties/windows/templates/windows.php.net.conf

+    RewriteRule ^/downloads/snaps         https://www.php.net/pre-release-builds.php#windows [NE]
+    RewriteRule ^/downloads/releases/(.*) https://downloads.php.net/~windows/releases/archives/$1
+    RewriteRule ^/downloads/(.*)          https://downloads.php.net/~windows/$1


Suggested change

RewriteRule ^/downloads/snaps https://www.php.net/pre-release-builds.php#windows [NE]

RewriteRule ^/downloads/releases/(.*) https://downloads.php.net/~windows/releases/archives/$1

RewriteRule ^/downloads/(.*) https://downloads.php.net/~windows/$1

RewriteRule ^/downloads/snaps https://www.php.net/pre-release-builds.php#windows [NE]

RewriteRule ^/downloads/releases/(.*) https://downloads.php.net/~windows/releases/archives/$1

RewriteRule ^/downloads/(.*) https://downloads.php.net/~windows/$1

This wasn't the right way, but it was broken and I updated. (We use tabs for indentation, and spaces for alignment in these files).

shivammathur · 2026-03-19T18:30:39Z

roles/properties/windows/templates/windows.php.net.conf

+	RewriteRule ^/$                       https://www.php.net/
+	RewriteRule ^/download$               https://www.php.net/downloads.php?os=windows


I think we should redirect both to the downloads page with os=windows as the requested url is related to windows and php.net being the home page is not windows specific.

I had thought www.php.net would be better, as the "main page" here just has PHP (on Windows) specific news. As news is on www.php.net (and not on https://www.php.net/downloads.php) that would be the better destination.

So I haven't changed this yet…

Yes. that makes sense.

shivammathur · 2026-03-19T18:32:49Z

roles/properties/windows/templates/windows.php.net.conf

+	RewriteRule ^/snapshots$              https://www.php.net/pre-release-builds.php#windows [NE]
+	RewriteRule ^/snapshots/$             https://www.php.net/pre-release-builds.php#windows [NE]
+    RewriteRule ^/downloads/snaps         https://www.php.net/pre-release-builds.php#windows [NE]
+    RewriteRule ^/downloads/releases/(.*) https://downloads.php.net/~windows/releases/archives/$1


That breaks the archive links on windows.php.net: /downloads/releases/archives/... becomes /~windows/releases/archives/archives/...

/downloads/releases/and sub directories on windows.php.net should redirect to ~windows/releases and corresponding subdirectories on downloads.php.net.

OK, I will change this.

But I had picked this specifically, as https://windows.php.net/download has links to
https://windows.php.net/downloads/releases/php-8.5.1-nts-Win32-vs17-x64.zip etc, and:
https://downloads.php.net/~windows/releases/php-8.5.1-nts-Win32-vs17-x64.zip doesn't exist, but
https://downloads.php.net/~windows/releases/archives/php-8.5.1-nts-Win32-vs17-x64.zip does.

shivammathur · 2026-03-19T18:34:31Z

roles/properties/windows/templates/windows.php.net.conf

+	ServerAlias {{ windows_domain_alias }}
+
+	ServerAdmin {{ systems_email }}
+	Redirect / https://qa.php.net/


We should not redirect windows.php.net webroot to qa.php.net, it should go to the downloads page with os=windows.

No, we should not redirect it to qa.php.net.

It should redirect to https://windows.php.net (this entry is for the http:// variant). I copied this over from the qa property and forgot to change this.

(In fact, this entry should never get used, as the CDN is configured to talk to the https:// variant anyway)

derickr

While redirecting makes sense, there are a couple of things I'm a little concerned about:

The info which is in the left sidebar of the windows.php.net page, in particular the information about Visual Studio. I remember when I first installed PHP for Windows myself (without a WAMP installer), that info saved my bacon.

I believe we should integrate that into https://wiki.php.net/internals/windows/stepbystepbuild_sdk_2, which already holds more up to date information.

Access to historical versions as https://www.php.net/releases/ looks to only contain the Linux versions.

The historical releases for Windows are (already) also available at https://downloads.php.net/~windows/releases/archives/ — I propose we add that link to the side bar of www.php.net/downloads.php as ([Windows](https://downloads.php.net/~windows/releases/archives/)) where it now says "Old Archives".

I'd also be interested to know how to get to QA releases for Windows. Looks like this is via https://www.php.net/pre-release-builds.php ? If so, where can I submit a PR to make that page a little more scannable ?

It lives at https://github.com/php/web-php/blob/master/pre-release-builds.php

Instructions on how to set up a local environment are at https://github.com/php/web-php/blob/master/README.md (it's git clone && cd web-php && php -S …).

I'm also not so sure about that "I want to use PHP for" dropdown - is it just me or does nothing change when you toggle between "Web development" and "CLI/library dev" ?

That's right, for Windows. We could add better instructions there for each. But when we set up the downloads page like this, no such instructions were available.

If you want to make a PR to add that, the following things need to be done (in https://github.com/php/web-php/blob/master/):

Create include/download-instructions/windows-downloads-web.php and include/download-instructions/windows-downloads-web.php containing the instructions for each variant, and then include windows-downloads.php.
Change https://github.com/php/web-php/blob/master/downloads-get-instructions.php#L58 to add a similar if/else for $options['osvariant'] === "{$options['os']}-downloads" as there is now for docker.

derickr · 2026-03-20T09:58:54Z

roles/properties/windows/templates/windows.php.net.conf

+	ServerAlias {{ windows_domain_alias }}
+
+	ServerAdmin {{ systems_email }}
+	Redirect / https://qa.php.net/


No, we should not redirect it to qa.php.net.

It should redirect to https://windows.php.net (this entry is for the http:// variant). I copied this over from the qa property and forgot to change this.

(In fact, this entry should never get used, as the CDN is configured to talk to the https:// variant anyway)

derickr · 2026-03-20T10:00:47Z

roles/properties/windows/templates/windows.php.net.conf

+	RewriteRule ^/$                       https://www.php.net/
+	RewriteRule ^/download$               https://www.php.net/downloads.php?os=windows


I had thought www.php.net would be better, as the "main page" here just has PHP (on Windows) specific news. As news is on www.php.net (and not on https://www.php.net/downloads.php) that would be the better destination.

So I haven't changed this yet…

derickr · 2026-03-20T10:02:58Z

roles/properties/windows/templates/windows.php.net.conf

+	RewriteRule ^/snapshots$              https://www.php.net/pre-release-builds.php#windows [NE]
+	RewriteRule ^/snapshots/$             https://www.php.net/pre-release-builds.php#windows [NE]
+    RewriteRule ^/downloads/snaps         https://www.php.net/pre-release-builds.php#windows [NE]
+    RewriteRule ^/downloads/releases/(.*) https://downloads.php.net/~windows/releases/archives/$1


OK, I will change this.

But I had picked this specifically, as https://windows.php.net/download has links to
https://windows.php.net/downloads/releases/php-8.5.1-nts-Win32-vs17-x64.zip etc, and:
https://downloads.php.net/~windows/releases/php-8.5.1-nts-Win32-vs17-x64.zip doesn't exist, but
https://downloads.php.net/~windows/releases/archives/php-8.5.1-nts-Win32-vs17-x64.zip does.

derickr · 2026-03-20T10:08:18Z

roles/properties/windows/templates/windows.php.net.conf

+    RewriteRule ^/downloads/snaps         https://www.php.net/pre-release-builds.php#windows [NE]
+    RewriteRule ^/downloads/releases/(.*) https://downloads.php.net/~windows/releases/archives/$1
+    RewriteRule ^/downloads/(.*)          https://downloads.php.net/~windows/$1


This wasn't the right way, but it was broken and I updated. (We use tabs for indentation, and spaces for alignment in these files).

jrfnl · 2026-03-20T10:50:24Z

The info which is in the left sidebar of the windows.php.net page, in particular the information about Visual Studio. I remember when I first installed PHP for Windows myself (without a WAMP installer), that info saved my bacon.

I believe we should integrate that into https://wiki.php.net/internals/windows/stepbystepbuild_sdk_2, which already holds more up to date information.

I don't think that's correct. This is not about building your own version of PHP. This is about running (pre-compiled) PHP on Windows. Those VS packages need to be installed on Windows to even be able to run PHP, so this is/should be end-user facing information, not internal information.

The internals page should include a directive to update the VS related info for Windows on the end-user facing pages when a different VS is used to build the standard Windows packages.

Access to historical versions as https://www.php.net/releases/ looks to only contain the Linux versions.

The historical releases for Windows are (already) also available at https://downloads.php.net/~windows/releases/archives/ — I propose we add that link to the side bar of www.php.net/downloads.php as ([Windows](https://downloads.php.net/~windows/releases/archives/)) where it now says "Old Archives".

👍🏻

I'd also be interested to know how to get to QA releases for Windows. Looks like this is via https://www.php.net/pre-release-builds.php ? If so, where can I submit a PR to make that page a little more scannable ?

It lives at https://github.com/php/web-php/blob/master/pre-release-builds.php

Instructions on how to set up a local environment are at https://github.com/php/web-php/blob/master/README.md (it's git clone && cd web-php && php -S …).

I'm also not so sure about that "I want to use PHP for" dropdown - is it just me or does nothing change when you toggle between "Web development" and "CLI/library dev" ?

That's right, for Windows. We could add better instructions there for each. But when we set up the downloads page like this, no such instructions were available.

If you want to make a PR to add that, the following things need to be done (in https://github.com/php/web-php/blob/master/):

Create include/download-instructions/windows-downloads-web.php and include/download-instructions/windows-downloads-web.php containing the instructions for each variant, and then include windows-downloads.php.

Change https://github.com/php/web-php/blob/master/downloads-get-instructions.php#L58 to add a similar if/else for $options['osvariant'] === "{$options['os']}-downloads" as there is now for docker.

Thanks for those pointers. I'll have a look when I have some brain space (which may be a while).

derickr · 2026-03-20T12:43:04Z

The info which is in the left sidebar of the windows.php.net page, in particular the information about Visual Studio. I remember when I first installed PHP for Windows myself (without a WAMP installer), that info saved my bacon.

I believe we should integrate that into https://wiki.php.net/internals/windows/stepbystepbuild_sdk_2, which already holds more up to date information.

I don't think that's correct. This is not about building your own version of PHP. This is about running (pre-compiled) PHP on Windows. Those VS packages need to be installed on Windows to even be able to run PHP, so this is/should be end-user facing information, not internal information.

@shivammathur fixed/addressed this, with php/web-php#1869

I've also updated the PR with the comments.

jrfnl · 2026-03-20T15:51:52Z

@shivammathur fixed/addressed this, with php/web-php#1869

I've also updated the PR with the comments.

Excellent! Thank you both!

jrfnl reviewed Mar 19, 2026

View reviewed changes

shivammathur reviewed Mar 19, 2026

View reviewed changes

derickr commented Mar 20, 2026

View reviewed changes

Add windows property

bc148ae

derickr force-pushed the add-windows-property branch from efb9f66 to bc148ae Compare March 20, 2026 13:48

derickr merged commit bc148ae into main Mar 20, 2026

		RewriteRule ^/$ https://www.php.net/
		RewriteRule ^/download$ https://www.php.net/downloads.php?os=windows

Conversation

derickr commented Mar 19, 2026

Uh oh!

jrfnl commented Mar 19, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

shivammathur Mar 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

derickr left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jrfnl commented Mar 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

derickr commented Mar 20, 2026

Uh oh!

jrfnl commented Mar 20, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

shivammathur Mar 19, 2026 •

edited

Loading

jrfnl commented Mar 20, 2026 •

edited

Loading