One addition: Actually, I am not trying to proxy one server (as I learned, this can be done by just assigning "proxy_set_header Host " someServer.akamai.com", but if possible several (I just reverted to one here for boiling down the issue). So I am using an upstream directive like this upstream akamaiBackend { server someServer1.akamai.com:80; server someServer2.akamby fatzopilot - Nginx Mailing List - English
Hi, thanks for your suggestion. Tried this well without success. It seems, I did not describe the issue properly, though. Just found a post (which you replied) describing a very similar situation: http://www.ruby-forum.com/topic/860524. The problem in both cases is IP sharing on the backend/upstream side and that the upstream hostname cannot be assigned and forwarded to the backend dynamicallby fatzopilot - Nginx Mailing List - English
Hi, I guess it is rather simple, but I am more of a coder than of an admin so not an expert in configuring webservers. I'd like to proxy an akamai proxy which relies on the full hostname being passed (IP is not enough). server { listen 80; server_name proxy.mydomain.com ## ssl on; location / { proxy_pass http://someServer.akamai.com:80; proxy_set_header Host $host; acby fatzopilot - Nginx Mailing List - English
Hi, I am interested in this as well (dynamic setup in a proxmox/openVZ environment where the hostname abstraction is quite useful as (virtual) network adapters change often) What is so bad about the following: * Try to resolve all names on startup and put them in the DNS in-memory cache (current behaviour) * just ignore non-resolvable hosts but log an error (new behaviour) * if there is a rby fatzopilot - Nginx Mailing List - English