I recently upgraded to PHP 4.3.10 on Apache 2 - Windows XP. The transition was smooth and successful, except one recurring little bug I keep finding.
The problem is HTTP authentication. It seems that PHP still manages to deliver auth headers to the browser (resulting in a password prompt), but neither PHP_AUTH_USER or PHP_AUTH_PW are passed back to the script.
I'm sure it's not a problem with my code (even broke phpMyAdmin), or apache (didn't make any configuration changes). Can anyone help mt fix the problem?
No. This only ragebaits clueless internet dwellers who have never worked in IT.
Yes bugs exist, but they affects unmanaged PCs, but also any problems are normally a tiny percentage that's greatly amplified by being on Reddit and by other clickbaity media.
In any mid-big business, the IT dept will manage every device, test updates on a few devices in a 'testing ring' before general deployment, and will generally just delay updates to be sure and that's it.
Agreed. I am responsible for 25,000 users across 17,000 devices and while it is far from perfect, our experience doesn’t drive me to rage about things.
Except these corporate IT Administrators could disable CoPilot in their environments if they wanted. This just seems like complaints from inexperienced Administrators
Question
Jambooo
I recently upgraded to PHP 4.3.10 on Apache 2 - Windows XP. The transition was smooth and successful, except one recurring little bug I keep finding.
The problem is HTTP authentication. It seems that PHP still manages to deliver auth headers to the browser (resulting in a password prompt), but neither PHP_AUTH_USER or PHP_AUTH_PW are passed back to the script.
I'm sure it's not a problem with my code (even broke phpMyAdmin), or apache (didn't make any configuration changes). Can anyone help mt fix the problem?
Thanks, Lee.
Link to comment
https://www.neowin.net/forum/topic/260290-php-4310-broke-http-authentication/Share on other sites
5 answers to this question
Recommended Posts