From nobody@FreeBSD.ORG Fri Nov 19 14:42:44 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 5D09814F3B; Fri, 19 Nov 1999 14:42:44 -0800 (PST)
Message-Id: <19991119224244.5D09814F3B@hub.freebsd.org>
Date: Fri, 19 Nov 1999 14:42:44 -0800 (PST)
From: mvh@ix.netcom.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: 'fetch' doesn't work for http when behind Inktomi Traffic-Server
X-Send-Pr-Version: www-1.0

>Number:         15001
>Category:       misc
>Synopsis:       'fetch' doesn't work for http when behind Inktomi Traffic-Server
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    des
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Fri Nov 19 14:50:01 PST 1999
>Closed-Date:    Thu Sep 28 02:22:44 PDT 2000
>Last-Modified:  Thu Sep 28 02:23:04 PDT 2000
>Originator:     Mike Harding
>Release:        3.3 Stable
>Organization:
Stamps.com
>Environment:
FreeBSD medusa.stamps.com 3.3-STABLE FreeBSD 3.3-STABLE #0: Thu Nov 18 18:35:28 PST\
 1999     mharding@medusa.stamps.com:/usr/src/sys/compile/STAMPS  i386
>Description:
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.

>How-To-Repeat:
Try to use fetch from an ISP which forces proxying via Inktomi
Traffic-server.
>Fix:
(hopefully) minor code changes to fetch?


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->des 
Responsible-Changed-By: des 
Responsible-Changed-When: Thu Jun 29 02:33:24 PDT 2000 
Responsible-Changed-Why:  
fetch(1) is mine. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=15001 

From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
To: freebsd-gnats-submit@freebsd.org
Cc:  
Subject: misc/15001
Date: 31 Aug 2000 16:41:17 +0200

 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
 
State-Changed-From-To: open->closed 
State-Changed-By: des 
State-Changed-When: Thu Sep 28 02:22:44 PDT 2000 
State-Changed-Why:  
Originator did not respond to request for additional information. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=15001 
>Unformatted:
