Newsgroups : Borland : borland.public.delphi.internet.winsock : 2007 Jan : Re: HTTP status 502 Bad Gateway

www.cryer.info
Managed Newsgroup Archive

Re: HTTP status 502 Bad Gateway

Subject:Re: HTTP status 502 Bad Gateway
Posted by:"Remy Lebeau (TeamB)" (no.spam@no.spam.com)
Date:Fri, 26 Jan 2007 10:24:00

"Philip von Melle" <philip.vonmelle@globetrotter.de> wrote in message
news:Xns98C46EEED3BEEphilipvonmelleglobe@207.105.83.66...

> I had thought so as well searching the source, but I get
> EIdHTTPProtocolExceptions "HTTP/1.1 502 Bad Gateway"

If you mean that you are getting it from TIdHTTP, then that is
correct.  The SERVER'S code reports an erro code of 502 for its own
reasons, and then the CLIENT wraps the erro code into an exception and
raises it.

> and I don't set anything like that in my OnCommandGet
> event handler

Of course not, because OnCommandGet is SENDING the error, not
RECEIVING it from another server.

> I am never touching TIdHTTPResponseInfo.ResponseCode

Then there is no way that 502 can be sent.  200 is the default
ResponseCode if you do not provide your own.

Pleae show your actual code.


Gambit

Replies:

none

In response to:

www.cryer.info
Managed Newsgroup Archive