Problem with GWT behind a reverse proxy - either nginx or apache

Question

I\'m having this problem with GWT when it\'s behind a reverse proxy. The backend app is deployed within a context - let\'s call it /context.

The GWT app works fine

Answer 1

I'm fairly sure the correct answer here is to patch the source and submit a bug report. Another option would be to run the GWT app at / on your backend.

I'd prefer the former, but the latter should work too. If you really needed things separated out into multiple contexts, use a different port number?