Inconsistencies in how HTTP headers are handled between servers

shadowq

Verified User
Joined
Dec 5, 2010
Messages
97
So, I've obviously set something up differently, but I have one DA host that is handling the HTTP headers differently, and I'm not sure why.

On all other DA hosts, sending a 401 or 503 still allows the webpage to be displayed correctly. However, on one host, I'm getting white pages with generic errors.

503 error-
1642820618692.png
401 error-
1642820652057.png


Now, I'm sure it's something simple, but can anyone please point me in the right direction?
 
So, I've obviously set something up differently, but I have one DA host that is handling the HTTP headers differently, and I'm not sure why.

On all other DA hosts, sending a 401 or 503 still allows the webpage to be displayed correctly. However, on one host, I'm getting white pages with generic errors.

503 error-
View attachment 5135
401 error-
View attachment 5136


Now, I'm sure it's something simple, but can anyone please point me in the right direction?
Files in private or public html , and http or https
 
Thanks for the reply!

Files in private or public html , and http or https
All in public_html, all https. It's the one entire host- dozens of users. I've looked through all the customisations to compare with other hosts, but can't find any discrepancies.
 
Thanks for the reply!


All in public_html, all https. It's the one entire host- dozens of users. I've looked through all the customisations to compare with other hosts, but can't find any discrepancies.
Yes ok but there are not privatehtml directory's then?

You also forgot to post versions?

DA , OS and much more .
 
Yes ok but there are not privatehtml directory's then?

You also forgot to post versions?

DA , OS and much more .
All domains have symlinks set up, private_html -> public_html.

DA 1.63.4
Centos 7
PHP-FPM 7.4
Nginx-apache
Apache 2.4
 
Thanks Ikkeben! Hopefully someone else can chime in and help. Not a very good look when something as simple as a typo when logging in to Webmail causes a 401 page, rather than a "Incorrect login, try again"
 
Thanks Ikkeben! Hopefully someone else can chime in and help. Not a very good look when something as simple as a typo when logging in to Webmail causes a 401 page, rather than a "Incorrect login, try again"
Search :

 
Thanks for the help. I've found those already, but I don't think it's quite what I want. On the contrary, my other DA hosts carry on as normal with a 502 or 401 header. As an example- on a correctly configured host, throw up a maintenance page with a 502 header on a domain, and the page still comes through, but with 502 headers. On the misconfigured host, throwing up a maintenance page with a 502 header, results in the ugly 502 page above.

So I guess my question is- how do you stop it forcing up the 502/401 error pages? I've tried searching everywhere, but I'm obviously not using correct terminology because can't find what I'm after.
 
As a tangible example-
Webmail 401 header on host A, shows the following ("Login failed" down the bottom, but still proceeds to load the page):
1642934857376.png

Webmail 401 header on host B, shows the following (complete error page):
1642935231090.png
 
As another tangible example:

Maintenance plugin on WP, serve up a "maintenance page" with a 503.
Host A:
1642935506544.png
Host B:
1642935370366.png
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>503 Service Unavailable</title>
</head><body>
<h1>Service Unavailable</h1>
<p>The server is temporarily unable to service your
request due to maintenance downtime or capacity
problems. Please try again later.</p>
</body></html>
 
Back
Top