HTTP 505 error message supported by NGINX?
reallfqq-nginx at yahoo.fr
Tue Aug 4 23:32:38 UTC 2015
It seems that by default nginx does not handle that HTTP code.
I just tried the following:
HEAD / HTTP/30.00
HTTP/1.1 200 OK
Date: Tue, 04 Aug 2015 23:27:43 GMT
Content-Type: text/html; charset=UTF-8
So if you overload the status code with 505, the reason won't change and
still be 'OK'.
That would explain why you saw '505 OK' which is an heresy...
On Wed, Aug 5, 2015 at 1:25 AM, nginxuser100 <nginx-forum at nginx.us> wrote:
> Thank you Francis. The body content did the trick ... not as aesthetically
> pleasing to the eyes as the NGINX's "hard-coded reason phrase", but it is
> better than a blank page.
> I did not understand what you meant by a config to control the reason
> Thanks again.
> Posted at Nginx Forum:
> nginx mailing list
> nginx at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx