The Un-Official Proxomitron Forum

Most people probably should just add
dragonfly.opera.com:
to bypass but...

If I
Open Opera10
Go to opera:config
In Developer Tools change https:// to http://https.. and save
Open new tab and Dragonfly
, I get 2 certificate warnings but Dragonfly does open.

If I change https:// to http://, Dragonfly opens without any warnings.

If I try this with SIDKI 2009-02-13 (UPDATE 06-06)
, the set changes the content type header of the application/xhtml+xml files, filters them, and breaks Dragonfly .
I added
dragonfly.opera.com $SET(0=a_web.i_cache:0.)
but still no Dragonfly.
I then changed
application/xhtml\+xml $SET(0=text/html)
in
$LST(Content-Types)
to
application/xhtml\+xml & (^$TST(uhost=dragonfly.opera.com)) $SET(0=text/html)
and I have Dragonfly.
ATM, I think the content type header is more important than the contents.

So, FWIW, I think you geeeee...ood people may be able to modify Dragonfly with Proxo.


Also a search for https in opera:config shows several address that may need special treatment:
https://autoupdate.opera.com/
https://auth.opera.com/xml
https://www.google.com/searchdomaincheck?format=domain


Have fun