![]() User agents SHOULD display any included representation to the user. These status codes are applicable to any request method. Server SHOULD send a representation containing an explanation of theĮrror situation, and whether it is a temporary or permanentĬondition. ![]() Except when responding to a HEAD request, the The 4xx (Client Error) class of status code indicates that the client.4xx (Client Error): The request contains bad syntax or cannot be fulfilled.Ultimately, while 418 is not explicitly defined in RFC 7231, it is still covered by the umbrella of 4xx (Client Error). The resulting entity body MAY be short and stout. Find a coffee maker." (the second server being the coffee maker). Any attempt to brew coffee with a teapot should result in the error code 418 Im a teapot. This is in the spirit of HTCPCP code 418, because if you attempt to BREW with a teapot, the appropriate response is "I'm not the kind of thing that can handle that request, but there may be others.". As far as the browser is concerned, it was a single request. NGINX then reroutes the traffic internally to the second server. So, if the first server determines the user is authenticated, it responds 418 I'm a teapot. The problem in this particular case, is the first server is the one that determines if the user is authenticated. ![]() One handles requests for unauthenticated users, and the second handles requests for authenticated users. I have nginx reverse-proxying requests to two separate HTTP servers.
0 Comments
Leave a Reply. |