HttpSendRequest
-
Hi all, Has anyone ever experienced or read of a problem where ::HttpSendRequest hangs on the INTERNET_STATUS_RECEIVING_RESPONSE status event? I am experiencing this problem intermitently in an application that I have written. I am using WININET syncrhonously an I have enabled the status callback, that is how I know the function is hanging at the INTERNET_STATUS_RECEIVING_RESPONSE event. My app will appear to work fine for quite a while, but then the thread that calls ::HttpSendRequest will hang. I detect this with a second thread to implement the timeout test as MSDN reports that this is the only reliable way to handle timeouts for versions of IE older than 5.5. After I detect the timeout, no requests work properly after that point until I restart my app. If anyone has insight to this I would really appreciate it. Thank you.
Build a man a fire, and he will be warm for a day
Light a man on fire, and he will be warm for the rest of his life! -
Hi all, Has anyone ever experienced or read of a problem where ::HttpSendRequest hangs on the INTERNET_STATUS_RECEIVING_RESPONSE status event? I am experiencing this problem intermitently in an application that I have written. I am using WININET syncrhonously an I have enabled the status callback, that is how I know the function is hanging at the INTERNET_STATUS_RECEIVING_RESPONSE event. My app will appear to work fine for quite a while, but then the thread that calls ::HttpSendRequest will hang. I detect this with a second thread to implement the timeout test as MSDN reports that this is the only reliable way to handle timeouts for versions of IE older than 5.5. After I detect the timeout, no requests work properly after that point until I restart my app. If anyone has insight to this I would really appreciate it. Thank you.
Build a man a fire, and he will be warm for a day
Light a man on fire, and he will be warm for the rest of his life!That's why I use Winsock. Todd Smith
-
That's why I use Winsock. Todd Smith
What about HTTPS support? Do you have any experience with that? Is it as simple as using the SSL functions instead of the regular socket functions? Thanks
Build a man a fire, and he will be warm for a day
Light a man on fire, and he will be warm for the rest of his life! -
What about HTTPS support? Do you have any experience with that? Is it as simple as using the SSL functions instead of the regular socket functions? Thanks
Build a man a fire, and he will be warm for a day
Light a man on fire, and he will be warm for the rest of his life!yep. But this depends on what are you doing - e.g. for client side apps the wininet is quite OK, but when talking about 24/7 apps it is better to use the pure winsock stuff + say few hundred lines for SSPI usage. And once you have some other SSL support(I think there are some on codeproject or look for OpenSSL or others) I will stick to it and don't want to see wininet any more in my life :) linx: SSL/TLS client/server for .NET[^] CSSLSocket[^]