When a trace fails, RemoteTerm currently returns a 504 Gateway Timeout. This works fine when not behind a proxy, but Cloudflare sees that as an error between the gateway and application and shows its own error screen instead.
Maybe that error message could be changed to 422?
The HTTP 422 Unprocessable Content client error response status code indicates that the server understood the content type of the request content, and the syntax of the request content was correct, but it was unable to process the contained instructions.
I think that is more logical than 504, which indicates that a server in front of the app did not get a response in time from the upstream server. The proxy may think that means the proxy itself instead of the application.
Error message from failed trace behind Cloudflare:
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When a trace fails, RemoteTerm currently returns a
504 Gateway Timeout. This works fine when not behind a proxy, but Cloudflare sees that as an error between the gateway and application and shows its own error screen instead.Maybe that error message could be changed to
422?I think that is more logical than
504, which indicates that a server in front of the app did not get a response in time from the upstream server. The proxy may think that means the proxy itself instead of the application.Error message from failed trace behind Cloudflare: