These are chat archives for IndySockets/Indy

26th
Feb 2017
Kudzu
@czhower
Feb 26 2017 14:33
502 is not an error from Indy, its an error code from the server that Indy is passing back to you.
"The 502 Bad Gateway error is an HTTP status code that means that one server on the internet received an invalid response from another server."
Sam B
@SamBirnbaum
Feb 26 2017 17:01
@czhower Thanks. I did research that and that is what I read, but I was wondering if that some settings in the Indy component can contribute to this problem. I don't have a problem accessing other websites with Indy. I did notice that there are newer dlls (libeay32.dll, ssleay32.dll) than what I currently have and could that be the cause.
@czhower I am currently using version 1.0.0g of the dlls and the new version is 1.0.2k. Do you know if the newer versions will function correctly with programs developed with the Indy components shipped with Delphi XE5 ?
Kudzu
@czhower
Feb 26 2017 17:22
@rlebeau would be the one to speak about SSL versions.
Sam B
@SamBirnbaum
Feb 26 2017 17:45
@czhower Thanks. Just tried the new versions with the site that is giving me the problem and the error persists. I will try the newer versions with other sites and will update with the results.
Sam B
@SamBirnbaum
Feb 26 2017 18:29
@czhower Ok, tried the newer versions accessing the sites that did NOT give me any problem before and all worked well. So It seems that this particular site might have an internal problem. Thanks again for your response and help.
Kudzu
@czhower
Feb 26 2017 21:36
glad to help