Reverse proxying Google Maps does not work with http-proxy

[jwchang0206]

ex) http://maps.google.com/maps/api/geocode/json?latlng=40.714224,-73.961452&sensor=true

With Nginx,

location /geocode {
    proxy_pass http://maps.google.com/maps/api/geocode
}

Works nicely.

But somehow with node-http-proxy,

httpProxy.createServer({
    router: {
        'localhost/geocode': 'maps.google.com/maps/api/geocode'
    }
}).listen(80);

Does not work.

I guess Nginx and node-http-proxy handles header differently :( ex) X-Forwarded-For, Referer and etc.

I want to use node-http-proxy :) instead of nginx to make this work.

Would you take some time to change header values when reverse proxying?

[jwchang0206]

Below is my example code snippet (jQuery code) that works well with Nginx's "proxy_pass"

$.getJSON( '/geocode/json?latlng=40.714224,-73.961452&sensor=true&language=en', function(data) {
    // successfully loaded data when data.status equals to "OK"
});

[indexzero]

Need some more info here:

1. What exact header values do you want changed? You mentioned x-forwarded-for and referer, others? The list needs to be exhaustive
2. What are the values of these headers now?
3. What should they be? And why?

[jwchang0206]

That was what I was asking you.. What those values of headers should be..

How nginx proxy headers are different from http-proxy headers..

and implementation.....

[indexzero]

I don't really know nginx ... we do set them.

[jwchang0206]

What about making exact same behavior as access from a browser? That would work since

ex) http://maps.google.com/maps/api/geocode/json?latlng=40.714224,-73.961452&sensor=true

url works through browsers :)

[jwchang0206]

@indexzero
Do node-http-proxy actually set headers as a client or as a server? I think nginx is sending headers as a client.

[coderarity]

It's because you're using a subdomain, see #217 (which doesn't have much yet, but I'm going to work on this soon). Or at least - I think it is =D

[indexzero]

Fixed along with #217