Bug 15001

Summary: 'fetch' doesn't work for http when behind Inktomi Traffic-Server
Product: Base System Reporter: mvh <mvh>
Component: miscAssignee: Dag-Erling Smørgrav <des>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description mvh 1999-11-19 22:50:01 UTC 
At work and home both ISPs force port 80 connections through an Inktomi
Traffic-Server caching proxy.  I have no way around this and I imagine a
number of people are in the same shape.  If I try a port build, like
www/apache13-php3, I can't fetch the patches from an http site -
this presumably happens for all http sites.  I can get around the 
problem by having squid use the proxy.

Presumably the Traffic-Server modifies the traffic is some manner that
'fetch' doesn't like, but it should be an easy fix - I could step through
the fetch attempt if somebody could give me some help building a
a debuggable fetch.

BTW - I have seen some discussion of other problems with Traffic-server,
including some company threatening to sue because it broke their
commerce system.  Our HTTP guys at work noticed that pages were not
being updated as they should be, as well.

Fix: 

(hopefully) minor code changes to fetch?
How-To-Repeat: Try to use fetch from an ISP which forces proxying via Inktomi
Traffic-server.
Comment 1 Dag-Erling Smørgrav freebsd_committer freebsd_triage 2000-06-29 10:33:24 UTC 
Responsible Changed
From-To: freebsd-bugs->des

fetch(1) is mine.
Comment 2 des 2000-08-31 15:41:17 UTC 
Are you still having trouble using fetch(1) from behind an Inktomi
traffic server? If so, please contact me for instructions about
obtaining debugging information.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no
Comment 3 Dag-Erling Smørgrav freebsd_committer freebsd_triage 2000-09-28 10:22:44 UTC 
State Changed
From-To: open->closed

Originator did not respond to request for additional information.