Header Filters automatically prepend https:// with connect?

[Stone-D]

Hi guys. I've been lurking here on and off throughout the years (Joined: May. 23, 2004!!!) and this, finally, is my first post.

After a mad filter building session around that time, I continued to use proxo unmodified in a school lab. Last week I decided to get dirty and clean up all the junk and rebuild some filters. During this I started to play with Half-SSL and during experimenting today stumbled into this.

Code:

Using this :
In = FALSE
Out = FALSE
Key = "URL : Half-SSL Uncaught (Out)"
Match = "(https://\0/)\1"
Replace = "$JUMP(https://https..\0)$LOG(R$DTM(c) : [HEADER] Half-SSL Test: \1)"

I get...

JumpTo: https://https..www.dropbox.com:443/
160 : [HEADER] Half-SSL Test: https://https..www.dropbox.c

+++GET 160+++
Using Proxy - localhost:4480
CONNECT https://https..www.dropbox.com:443/ HTTP/1.1
User-Agent: Opera/9.80 (Windows NT 6.1; U; en) Presto/2.10.229 Version/11.61
Host: https..www.dropbox.com
Proxy-Connection: Keep-Alive
+++CLOSE 160+++
BlockList 161: in Bypass-SSL, line 29

Code:

Using THIS, however :
In = FALSE
Out = FALSE
Key = "URL : Half-SSL Uncaught (Out)"
Match = "(https://\0/)\1"
Replace = "$JUMP(http://https..\0)$LOG(R$DTM(c) : [HEADER] Half-SSL Test: \1)"

I get...

JumpTo: https://http://https..www.dropbox.com:443/
162 : [HEADER] Half-SSL Test: https://http://https..www.dr

+++GET 162+++
Using Proxy - localhost:4480
CONNECT https://http://https..www.dropbox.com:443/ HTTP/1.1
User-Agent: Opera/9.80 (Windows NT 6.1; U; en) Presto/2.10.229 Version/11.61
Host: http
Proxy-Connection: Keep-Alive
+++CLOSE 162+++

wat?

[sbk]

wouldn't you want to match http, then replace with https?
i didn't try this myself, but is this better:

Code:

In = FALSE
Out = FALSE
Key = "URL : Half-SSL Uncaught (Out)"
Match = "(http://\0)\1"
Replace = "$JUMP(https://\0)$LOG(R$DTM(c) : [HEADER] Half-SSL Test: \1)"

[Stone-D]

Indeed, but I'm trying to do the opposite: redirect https:// to http://https..

[sbk]

(Feb. 14, 2012 02:15 PM)Stone-D Wrote:  Indeed, but I'm trying to do the opposite: redirect https:// to http://https..

i think we need an example of typical "in" (as proxo receives from your net connection) and desired "out" (as proxo sends to browser). are these correct?
"in":
https://www.dropbox.com:443/photos/pifflepotamus
want "out":
http://https..www.dropbox.com:443/photos/pifflepotamus
1. do you need to remove the :443 ?
2. looks to me partially like some url commands, such as dbug etc and half-ssl in:
http://prxbx.com/forums/showthread.php?t...6#pid16056
with which i am not familiar. :/
(file search shows half-ssl is discussed in 2003 ReadMe.txt and a lot of sidki files, ptron, ptxt, faq...)



So, i guess you don't want "out":
http://www.dropbox.com:443/photos/pifflepotamus

________
looking again at your first post..
maybe you have both filters enabled, so log window after second filter shows results of both filters?
maybe you need to add a $STOP() to prevent filter matching it's own results. but i think you see that in log window.

i find it easier to follow what happens when i give each version of a filter its own version number/letter

[JJoe]

(Feb. 14, 2012 10:36 AM)Stone-D Wrote:  wat?

I remember coming to the conclusion that Scott Lemmon did this on purpose.
If the Proxomitron allowed a redirect from https to http, half-SSL might be too seamless.

I'm not sure how current browsers respond to an https to http redirect.

HTH

[Stone-D]

sbk: I'm trying to intercept https web requests sent by a third party app to my browser - in this case, merely clicking "Launch Dropbox website" in dropbox's tray menu.

JJoe: Unavoidable then? Gah!

[whenever]

(Feb. 15, 2012 04:40 AM)JJoe Wrote:  If the Proxomitron allowed a redirect from https to http, half-SSL might be too seamless.

That's why I made ProxHTTPSProxy.

(Feb. 15, 2012 04:40 AM)JJoe Wrote:  I'm not sure how current browsers respond to an https to http redirect.

I think browsers are OK with that. Proxomitron just can't do that kind of redirect.