Jump to content

HTMLValidator.com

Members
  • Content Count

    31
  • Joined

  • Last visited

Everything posted by HTMLValidator.com

  1. In the RequestDone event of a TSslHttpCli object, a user is reporting that he's getting Error 10053 but StatusCode is 200 and ReasonPhrase is "OK". This seems to only happen on his "test" server and not his "production" server. The "test" server has a lot less resources and it's being hit hard with a lot of requests but I'm not sure that explains what's happening. Why would Error be 10053 but StatusCode and ReasonPhrase indicate no error? UPDATE: Customer adds: "The test and production servers have same configuration files (Apache + nginx), same settings for SSL/TLS (ciphers...). The difference is that the test server uses self-generated certificate, while the production server has certificate issued by Certificate Authority. Most (if not all browsers) do not like self-generated certificate (or bad or obsolete certificates) and issue warning with such URLs. The problem is that only some links (5000+) got 10053 error, not all (300K+ if I remember well) if I refer to the statistics shown during run, so probably the server load would be part of the problem, not the protocol itself." Thank you!
  2. HTMLValidator.com

    Error is 10053 but StatusCode is 200

    Thank you all. This is regarding a link checker in my software... so if the Error is 10053 and StatusCode is 200 then I'll just assume the link exists and ignore the 10053 error.
  3. HTMLValidator.com

    Error is 10053 but StatusCode is 200

    Thanks... but if the connection was aborted, why a StatusCode of 200 and ReasonPhrase of "OK"? Perhaps the connection was aborted after the status was received? Interesting: https://www.chilkatsoft.com/p/p_299.asp
  4. HTMLValidator.com

    Can't compile samples on CB2009

    Thanks! Hopefully these problems won't be an issue the next time I update ICS.
  5. HTMLValidator.com

    Can't compile samples on CB2009

    Same problem here with 10.3.2. Just updated my ICS components to the latest recommended release (8.61). I get these errors just trying to compile an empty C++ VCL project with a TSslHttpCli component on it. [bcc32c Error] sspi.h(65): You must define one of SECURITY_WIN32, SECURITY_KERNEL, or [bcc32c Error] sspi.h(66): SECURITY_MAC [bcc32c Error] sspi.h(2288): unknown type name 'PUNICODE_STRING' I defined 'SECURITY_WIN32' in the project options but now I get this error: [bcc32c Error] OverbyteIcsSspi.hpp(88): expected ')' OverbyteIcsSspi.hpp(88): to match this '(' Commented out the SEC_E_INVALID_HANDLE line in the *.hpp files (for 32-bit and 64-bit) and now it compiles and builds (both 32-bit and 64-bit)... still testing though.
×