<HEAD><TITLE>Httpver Not Supported</TITLE></HEAD>
<BODY BGCOLOR="white" FGCOLOR="black"><H1>Httpver Not Supported</H1><HR>
<!-- (This "Httpver Not Supported" response (HTTP status 505) comes from a Traf
when I try to browse the Web with Lynx. Why? Well, my ISP is using
digex.net. digex.net has instituted mandatory router-based web
proxying, using Inktomi's Traffic Server -- much like Singapore has.
(Although perhaps Singapore is using different software.) Now it seems
Traffic Server is having some problems.
I get the same document with Netscape 3.0, with Lynx 2.5, and with Lynx
2.8.rel2. For a while, I was getting it on every HTTP request; now it
seems less common.
I can only assume that everyone else on digex.net had the same
experience today. Me, I set up a crude web-proxy (a shell script) on a
machine connected through PSINet and used that. But not everyone has
What I want to know is: how can Digex do this? I'm frustrated every
time problems with their Traffic Server configuration cut me off from
the rest of the Web. Isn't it fraud to claim to offer Internet access
and then filter it this way, preventing outgoing packets from going out
if they're to port 80/tcp?
I'm not quite willing to change ISPs because of this, but it *is* quite
-- <email@example.com> Kragen Sitaker <http://www.pobox.com/~kragen/> Computers are the tools of the devil. It is as simple as that. There is no monotheism strong enough that it cannot be shaken by Unix or any Microsoft product. The devil is real. He lives inside C programs. -- firstname.lastname@example.org