|
ProxHTTPSProxyMII: Development
|
|
Oct. 21, 2015, 02:44 AM
Post: #177
|
|||
|
|||
|
RE: ProxHTTPSProxyMII: Development
First of all, thank you so much for this excellent piece of software. It's vastly extended the useful life of good ole' Proxomitron, for which there's no true modern replacement.
But I'm having a little issue here. ProxHTTPSProxyMII doesn't seem to be honoring the "connection:close" header when using HTTPS. This works fine for standard HTTP 1.1, but not for encrypted connections. I also tried not sending a connection header at all (which usually has the same effect as connection:close), going as far as forcing "Send only HTTP/1.0 requests" and "Local connections persist for..." from Proxomitron itself, both of which actually work ok with the now obsolete SSleay/openSSL option (not that I'm using it, but I make mention thereof for the very argument's sake), yet it all seems to be completely ignored by ProxHTTPSProxyMII, thus whatever connection's established, it will not be closed with enough immediacy and actually be handled as keep-alive (I can understand why this is a desirable default behavior under regular, everyday circumstances, but to me it is a necessity to go the other way around, even as potentially wasteful as non-persistent HTTPS connections may be, though they're perfectly valid) In short, it is my request, if you should hearken unto it, that "HTTPS 1.0 connections" or so to speak, be made viable, so that both sending no connection header and sending a close connection header, will operate exactly as they would for standard HTTP connections. Best regards and sorry for the inconveniences. "He that believeth on the Son hath everlasting life: and he that believeth not the Son shall not see life; but the wrath of God abideth on him" - John 3:36 |
|||
|
« Next Oldest | Next Newest »
|

Search
Member List
Calendar
Help




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