You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I got the ingress error backend working and can now serve custom error pages. Perfect!
One requirement for us is, that the error pages are internationalized, therefore I would like to rely on the http headers of the client (Accept-Language). But when requesting the error page the nginx does only provide the X-Format and X-Code headers.
Maybe it would be a good idea to pass all other headers to the error backend?
The text was updated successfully, but these errors were encountered:
@foxylion added to the TODO list for the next version. The reason why the headers are not passed is because we make a subrequest using lua here and we only specify the status code.
I will open a PR to pass all the headers from the request.
I got the ingress error backend working and can now serve custom error pages. Perfect!
One requirement for us is, that the error pages are internationalized, therefore I would like to rely on the http headers of the client (
Accept-Language
). But when requesting the error page the nginx does only provide theX-Format
andX-Code
headers.Maybe it would be a good idea to pass all other headers to the error backend?
The text was updated successfully, but these errors were encountered: