Sunday, April 28, 2013

Re: Apache ProxyPass does not return errors, only 500 (Internal Server Error)

I'm using 
RequestHeader edit X-GWT-Module-Base ^(http)://([^/]+)/(.*)$ $1://$2/babyCenter/$3

and it works. :) Thanks a lot.

Dne petek, 19. april 2013 23:39:19 UTC+2 je oseba Thomas Broyer napisala:

On Friday, April 19, 2013 9:20:49 AM UTC+2, Gregor Kovač wrote:

I have two ProxyPass directives:

ProxyPass /client/  <Location /client/>      RequestHeader edit X-GWT-Module-Base ^(.*)/client/(.*)$ $1/client/$2  </Location>    ProxyPass /  <Location />      RequestHeader edit X-GWT-Module-Base ^(.*)/(.*)$ $1/client/$2  </Location> is running Glassfish on port 8080 and is URL to a GWT based application. Both proxy's work OK ,except when it comes to an error on the Glassfish side. If I go via /cllient/ proxy then I see the actual error that was produced on the Glassfish side. If I go via / proxy then I only see "Error 500 The call failed on the server, please see server log". I've tried settingProxyErrorOverride Off, but it didn't help.

Why don't I see the error via / proxy? I think that the X-GWT-Module-Base header gets edited wrong. This apache configuration is done by

Assuming X-GWT-Module-Base contains http://myserver/foo/bar, there's no reason it wouldn't be rewritten as http:/client//myserver/foo/bar, http://client/myserver/foo/bar or http://myserver/foo/client/bar instead of the http://myserver/client/foo/bar you're expecting.
You have to rework your regexp. Maybe mapping something like ^(https?)://([^/]+)/(.*)$ to $1://$2/client/$3

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment