You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
secure.php.net redirect omits slash to separate domain and path #1684
The redirect that redirects secure.php.net to php.net removes any "/" after php.net which breaks all redirects that include paths on secure.php.net.
This happens e.g. for the "!php" bank for DuckDuckGo, which seem to use "https://secure.php.net/manual-lookup.php?pattern={{{s}}}" under the hood.
-> https://www.php.netmanual-lookup.php?pattern=explode (missing a / after php.net)
Expected behavior
The returned location header in the redirect response should keep the "/", in the above example, that would be https://www.php.net/manual-lookup.php?pattern=explode
Screenshots
Seemingly the bang "!php" configuration for DuckDuckGo
(partial) curl response from my local machine for curl -v --head https://secure.php.net/manual-lookup.php?pattern=explode
Additional context
I'm not sure if this is the right place to report this, if not, please "redirect" me to the proper place :)
Right after the creation of this issue, I'll fill out the above form on DuckDuckGo to ask them to change the bang source to https://www.php.net/manual-lookup.php?pattern={{{s}}} referencing this issue, since this is where the secure.php.net redirect wants to redirect me to.
I've written to DDG to point the !php bang directly to www.php.net and linked them to this ticket, but didn't get any response from them till now. When I get something, I'll make sure to post the response in this ticket.
Activity
cngJo commentedon Dec 4, 2025
For transparency, full message I sent to DDG on https://duckduckgo.com/newbang
(email hidden on purpose)
[-]secure.php.net redirect is broken[/-][+]secure.php.net redirect omits slash to separate domain and path[/+]derickr commentedon Dec 8, 2025
I'll fix this on the CDN side, but it would be great if DDG would stop using "secure.php.net". Would you be able to convince them to do that?
derickr commentedon Dec 8, 2025
It's now fixed on the PHP side.
cngJo commentedon Dec 8, 2025
Awesome! Thank you, @derickr 🎉
I've written to DDG to point the
!phpbang directly to www.php.net and linked them to this ticket, but didn't get any response from them till now. When I get something, I'll make sure to post the response in this ticket.fix(php): use www.php.net instead of secure.php.net
fix(php): use www.php.net instead of secure.php.net