[Mailman-Users] "invalid uri"

[Bek Oberin]

Paul Tomblin wrote:
> Quoting Bek Oberin (gossamer at tertius.net.au):
>> Paul Tomblin wrote:
>>> Quoting Bek Oberin (gossamer at tertius.net.au):
>>>>                                   Bad Request
>>>>    Your browser sent a request that this server could not understand.
>>>>    Invalid URI in request GET mailman/admindb/asrmel HTTP/1.0
[...]
> That's bizarre.  I don't see how going to any normal URL could cause
> a "GET" command without a leading slash to be sent to the httpd. 
> Unless you have a URL like "http:mailman/admindb/asrmel" somewhere
> on your site and that's what you're clicking to get there.  Because
> if you were to type the URL
> http://xcski.com/mailman/admindb/upstateav, that should cause your
> browser to say "hmmm, ok, that's a url on xcski.com, so I'll connect
> to port 80 on xcski.com, and issue the command ``GET
> /mailman/admindb/upstateav HTTP/1.0''".

Okay, I figured it out.  It   seems to be a weird bug that
happens in Lynx (at least) when you have http_proxy set to
the null string.  If I  unset the variables (like I should
have done in the first place) then it starts to work again

I remain, as always, baffled.

bekj

-- 
: --Hacker-Neophile-Eclectic-Geek-Grrl-Queer-Disabled-Boychick--
: gossamer at tertius.net.au   http://www.tertius.net.au/~gossamer/
: "Why is Perl so much worse than Python?" That's easy.  Perl is
: worse than Python because people wanted it worse.  -- Larry Wall