Closed Bug 233365 Opened 21 years ago Closed 20 years ago

Mail Window renders HTML ignoring HTTP proxy settings

Categories

(SeaMonkey :: MailNews: Message Display, defect)

defect
Not set
major

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: doug, Assigned: sspitzer)

Details

User-Agent:       
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

HTML-formatted email is rendered automatically in the mail window without
regards for the HTTP proxy.  An example is spam ads.  The HTML email is rendered
with the images from the remote host, even though that host is blocked by a
content filtering proxy.  I would think the Mail Windows should honor proxy
settings.

Reproducible: Always
Steps to Reproduce:
1. 
2.
3.
bug 205947 ?

*** This bug has been marked as a duplicate of 23728 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
I think more information is needed here.

What is your proxy config, what should be blocked, and what is not being blocked?
Status: RESOLVED → UNCONFIRMED
QA Contact: esther → benc
Resolution: DUPLICATE → ---
My proxy config is:  Squid HTTP caching proxy with SquidGuard for content
filtering.  Squid is listening on port 80 on another host.  No authentication is
necessary.  

Using the Mozilla 1.6 browser with Manual Proxy configuration set to my proxy
host and port, the SquidGuard content filter correctly redirects requests for
HTML from blacklisted sites.  The browser is effectively blocked from viewing
that content.

However, when using Mozilla 1.6 Mail in 3-pane mode, if I get HTML-formatted
email with in-line images from sites in my blacklist, the Mail window displays
all HTML, including in-line images downloaded from "blacklisted" sites.  Hence
my conclusion that Mail Window does not honor HTTP proxy settings.  

I would think that the Mail Window should render all in-line HTML, but defer to
the HTTP proxy when attempting to GET content from the internet.  Does that make
sense?
Okay. That makes a lot more sense. I've never looked at this myself, so I din't
know what the expected behavior is.
Doug:

The best way to confirm the problem, is to use netstat right after you open the
message. It lists the network connections, so you would see a connection to the
offending content server, rather than your proxy.

Can you create a sample email that demonstrates the problem? This is fairly
different from our understanding of how HTML network loading should occur.
As noted in bug 257542 comment 2, I am seeing HTTP proxying work for 
Thunderbird; using the same test, I'm seeing it work for Mozilla 1.7.2.

Doug Poland, are you sure the images were remote and not included in the 
message?
Product: Browser → Seamonkey
No response from reporter; =>WFM

Doug Poland, feel free to reopen bug, but address comment 6 & 7.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago20 years ago
Resolution: --- → WORKSFORME
Using Mozilla 1.7.3 now and it is honoring the proxy setting in
Preferences-->Advanced-->Proxies.  BTW, I monitored the app by watching my squid
logs.  All http traffic is passed through squid and, when I filed this bug,
images rendered in the mail preview window didn't appear in squid logs.  Now
they do!  Thanks much!
v

Thanks for the response
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.