|
ProxHTTPSProxy, a Proxomitron SSL Helper Program
|
|
May. 22, 2010, 02:28 AM
(This post was last modified: May. 22, 2010 02:45 AM by Graycode.)
Post: #29
|
|||
|
|||
RE: ProxHTTPSProxy, a Proxomitron SSL Helper Program
(May. 22, 2010 02:19 AM)whenever Wrote: Graycode, what's the difference between reading character by character and reading a bunch from a socket? Sorry, I removed that post when I saw you'd responded to JJoe. Did that to avoid interfering with your project. I'll re-upload it if you want, or you can (it's Your ideas & project). The character-by-character was to account for commenting out the setblocking(0), while also being able to accommodate either a short or a long URL. If setblocking(0) does what I think it does then it's unlikely to get the browser's headers with the same packets that completed the SSL handshake. Without waiting (blocking) for data the read() wouldn't have anything in the queue, perhaps leading to that exception. Sometimes a bit of the data might be there, sometimes not. So I figured that using socket blocking was better, and then grabbing the URL char-by-char seemed a reasonable solution to making sure the minimum amount of expected data had arrived before proceeding. |
|||
|
« Next Oldest | Next Newest »
|

Search
Member List
Calendar
Help





![[-]](images/ONi/collapse.gif)