We use cookies to improve your experience. No personal information is gathered and we don't serve ads. Cookies Policy.

ExpressionEngine Logo ExpressionEngine
Features Pricing Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University
Log In or Sign Up
Log In Sign Up
ExpressionEngine Logo
Features Pro new Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University Blog
  • Home
  • Forums

HTTP Authentication on Template fails on PHP 7.3 but works on 5.6 - SOLVED

Development and Programming

gprobst's avatar
gprobst
23 posts
4 years ago
gprobst's avatar gprobst

SOLVED On the off chance that anybody else runs into this, I realized that I was using suphp as my PHP handler on my previous server (and on the PHP 5.6 on the new one), and the new server had cgi set as the default PHP handler for PHP 7.3. As soon as I set to the suphp, everything worked perfectly!

I recently migrated an EE 5.3.2 site from a CentOS 6 server to a CentOS 7 server, and everything works fine except for a page that I have password protected using EE’s built-in HTTP Authentication option in the template settings. It was working fine on the previous server, but it just is stuck in an endless loop of not accepting login credentials on the new server.

Both the old server and the new one were running PHP 7.3 and have the exact same php.ini file. Neither were/are using PHP-FPM. The weird thing is that if I roll back to PHP 5.6 on the new server HTTP Authentication works fine on the page. Unfortunately, PHP 5.6 is past EOL, so that’s obviously not a solution to the problem. I compared the php.ini file for PHP 5.6 to the one for PHP 7.3, and there were no obvious glaring differences.

Anyone else experience HTTP Authentication not working in PHP 7.3? If so, have you found a solution? Thanks!

👍 1
       
Robin Sowell's avatar
Robin Sowell
13,158 posts
4 years ago
Robin Sowell's avatar Robin Sowell

Thanks for the update- I would never have thought of that. I’d expect it to work on cgi as well. It might be an EE bug that it’s not, or it could be a server quirk. Definitely something we should keep an eye out for!

       

Reply

Sign In To Reply

ExpressionEngine Home Features Pro Contact Version Support
Learn Docs University Forums
Resources Support Add-Ons Partners Blog
Privacy Terms Trademark Use License

Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.