SOLVED!
First one thing about your comment Michael. A numeric IP is necessary whenever you are using variables in the proxy path. This is because if the final string needs to be built during runtime nginx asks a resolver ro resolve the final address. And of course there is no resolver for localhost...
Anyway, the solution for MY problem took quite a while. In the end I was sitting and analyzing every bit of the http traffic between all the remote sites and the webserver. There was no difference at all. So what's going on here?
I cleared the cache and history of the malfunctioning (firefox) browser - with no luck. Restarted browsers - with no luck.
In the end I was sure that there is absolutely nothing different between the working and the not working browsers!
Well, except for one thing: One of the not working browser is behind a proxy.
So i tried another browser (IE), and e voila, worked.
And now guess what: From then on that browser that never worked before now works!
On another machine I made the evil browser work by installing "fiddler", a web traffic analyzer.
Can anybody tell me why these steps did help? Especially the proxy thingy. For that to make any difference the other browser must have had some communication with the proxy that caused the proxy to do something different from then on. Very obscure... Keep in mind that http traffic on both evil browsers was exactly the same before and after!
Don't know if someone will find this helpful, but never mind...
ako673de
First one thing about your comment Michael. A numeric IP is necessary whenever you are using variables in the proxy path. This is because if the final string needs to be built during runtime nginx asks a resolver ro resolve the final address. And of course there is no resolver for localhost...
Anyway, the solution for MY problem took quite a while. In the end I was sitting and analyzing every bit of the http traffic between all the remote sites and the webserver. There was no difference at all. So what's going on here?
I cleared the cache and history of the malfunctioning (firefox) browser - with no luck. Restarted browsers - with no luck.
In the end I was sure that there is absolutely nothing different between the working and the not working browsers!
Well, except for one thing: One of the not working browser is behind a proxy.
So i tried another browser (IE), and e voila, worked.
And now guess what: From then on that browser that never worked before now works!
On another machine I made the evil browser work by installing "fiddler", a web traffic analyzer.
Can anybody tell me why these steps did help? Especially the proxy thingy. For that to make any difference the other browser must have had some communication with the proxy that caused the proxy to do something different from then on. Very obscure... Keep in mind that http traffic on both evil browsers was exactly the same before and after!
Don't know if someone will find this helpful, but never mind...
ako673de