nginx error after trying to upload images

[B.R.]

Without much information about the context/usage of you application, what
follows is pure speculation.


*First, please note you are on the nginx mailing list, where you might ask
for help about handling nginx itself.*
*Bumping in unexpected 3rd-party servers is out of scope.*

I do not see why ISP would use proxies redirecting URI to others...
Routing is not done that way ^^

Strange nginx in the middle might be the sign of cmpromission/tampering.

Early checks I would do:
Are you sure about your DNS resolution (ie domain name resolves to correct
IP)?
Are you sure the target machine is legit?
Traceroutes might reveal which nodes your traffic is going through. Any
oddity is to be investigated.

Finally, using SSL certificates might prevent another machine impersonating
the one you are trying to contact.
---
*B. R.*


On Sat, Jun 14, 2014 at 4:38 PM, Roy Phillips <roy at xdam.com> wrote:

> Hi all,
>
> Anyone have an idea why we would get this error when trying to upload
> image? I am stumped  as to why nginx erro would be mixed in with this. Is
> the customers ISP using nginx and blocking our upload?
>
>
>
> Thank you,
> Roy Phillips
> XDAM Support
> roy at xdam.com
>
> http://www.xdam.com
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140614/4504c8d9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Unknown[1].png
Type: image/png
Size: 48758 bytes
Desc: not available
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140614/4504c8d9/attachment-0001.png>