Closed Bug 40813 Opened 25 years ago Closed 25 years ago

Incorrect broken links when using 'adzapper' proxy

Categories

(Core :: Networking, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED INVALID

People

(Reporter: mcguirk, Assigned: gagan)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/4.61 [en] (X11; I; Linux 2.2.12-20 i686) BuildID: 2000042708 I'm using an ad filtering proxy called 'adzapper' that is available at http://www.zaplet.org/adamf/adzapper/. When following a link, I'll often get a broken link error from the destination site for a link that is not really broken. Reproducible: Sometimes Steps to Reproduce: (1) Start Mozilla. (Configured to use adzapper proxy.) (2) Go to www.jabber.org. (3) Click 'Documentation'. (4) Click 'Jabber Technology Overview'. Actual Results: About 90% of the time I get a "Not Found" from docs.jabber.org (the target of the link). Sometimes it does work, though. If I press "reload" on the "Not Found" page, the page comes up correctly. The page always comes up correctly if I don't use the proxy, or if I use Netscape 4 with or without the proxy. Expected Results: The page should always show up correctly the first time.
This happens lots of other places, too (I just saw it happen when trying to follow the 'Bugzilla Helper' link from http://bugzilla.mozilla.org). I think having the target of the link on a different host than the source may be significant.
OK, so it looks like the bug is actually in adzapper. Its handling of Keep- Alive seems very broken.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
vrfy
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.