Post Reply 
SSL stylesheets at wellsfargo.com
Oct. 08, 2010, 03:26 AM (This post was last modified: Oct. 08, 2010 04:23 PM by sidki3003.)
Post: #1
SSL stylesheets at wellsfargo.com
I have no idea if this quirk is particular to this release or not, but when using https filtering and visiting https://www.wellsfargo.com on my system, Firefox 3.6.9 does not load the site's css code and the page is displayed in plain text. This problem does not happen with IE8 or Opera 10.70 beta. I'm using the light mode of this beta configuration with no substantial changes other than allowing https filtering.
Add Thank You Quote this message in a reply
Oct. 08, 2010, 04:31 AM (This post was last modified: Oct. 09, 2010 01:06 AM by JJoe.)
Post: #2
RE: Beta Config (Sep 19 2010)
(Oct. 08, 2010 03:26 AM)wammie Wrote:  I have no idea if this quirk is particular to this release or not

It isn't.
Please start a new topic in Proxomitron Program and delete this one.

I'm out of time for tonight.
Add Thank You Quote this message in a reply
Oct. 08, 2010, 04:23 PM
Post: #3
RE: SSL stylesheets at wellsfargo.com
Topic split.
Add Thank You Quote this message in a reply
Oct. 08, 2010, 04:26 PM (This post was last modified: Oct. 08, 2010 04:48 PM by sidki3003.)
Post: #4
RE: SSL stylesheets at wellsfargo.com
(Oct. 08, 2010 03:26 AM)wammie Wrote:  I have no idea if this quirk is particular to this release or not, but when using https filtering and visiting https://www.wellsfargo.com on my system, Firefox 3.6.9 does not load the site's css code and the page is displayed in plain text. This problem does not happen with IE8 or Opera 10.70 beta. I'm using the light mode of this beta configuration with no substantial changes other than allowing https filtering.

Proxomitron is using (has to use) a self-signed certificate.

Here's what's apparently happening:
You visit wellsfargo.com, get some flavor of "self signed cert" warning from your browser, confirm it for wellsfargo.com.
However, the external stylesheet is served from https://a248.e.akamai.net/ .
If the latter were an HTML main page or frame, you'd have the chance to confirm the exception, but it isn't, it's a CSS.

Since you're using the beta, you could - as a test- click "Show 2 CSS" in the Prox menu (i *think* it's enabled for light mode too), and confirm the warning there.

If the layout is okay after reload, then there is a general work-around:
Half-SSL is a method that causes Proxomitron to transfer the decrypted page to the browser as is. The browser thinks it is receiving a normal HTTP document. You can activate that with the header filter "! |||||||||||| 2.2 Use Half-SSL" (number may vary with config version).
Add Thank You Quote this message in a reply
Oct. 09, 2010, 06:58 AM (This post was last modified: Oct. 09, 2010 06:58 AM by wammie.)
Post: #5
RE: SSL stylesheets at wellsfargo.com
(Oct. 08, 2010 04:26 PM)sidki3003 Wrote:  
(Oct. 08, 2010 03:26 AM)wammie Wrote:  I have no idea if this quirk is particular to this release or not, but when using https filtering and visiting https://www.wellsfargo.com on my system, Firefox 3.6.9 does not load the site's css code and the page is displayed in plain text. This problem does not happen with IE8 or Opera 10.70 beta. I'm using the light mode of this beta configuration with no substantial changes other than allowing https filtering.

Proxomitron is using (has to use) a self-signed certificate.

Here's what's apparently happening:
You visit wellsfargo.com, get some flavor of "self signed cert" warning from your browser, confirm it for wellsfargo.com.
However, the external stylesheet is served from https://a248.e.akamai.net/ .
If the latter were an HTML main page or frame, you'd have the chance to confirm the exception, but it isn't, it's a CSS.

Since you're using the beta, you could - as a test- click "Show 2 CSS" in the Prox menu (i *think* it's enabled for light mode too), and confirm the warning there.

If the layout is okay after reload, then there is a general work-around:
Half-SSL is a method that causes Proxomitron to transfer the decrypted page to the browser as is. The browser thinks it is receiving a normal HTTP document. You can activate that with the header filter "! |||||||||||| 2.2 Use Half-SSL" (number may vary with config version).
Enabling the "Use Half-SSL" option has solved this issue in Firefox. Thanks!
Add Thank You Quote this message in a reply
Oct. 10, 2010, 06:44 AM
Post: #6
RE: SSL stylesheets at wellsfargo.com
It seems to be a Firefox bug more than a Proxomitron issue.

We will have the same issue if the server a248.e.akamai.net has a wrongly configured or expired certificate, even if we are not using Proxomitron.
Add Thank You Quote this message in a reply
Post Reply 


Forum Jump: