Bug#265128: polipo: Here's another example

2005-01-13 Thread Greg Kochanski
If I could stick my $0.02 in? A lot of these disagreements about "bug or wishlist" are really disagreements about whose perspective to adopt. From the maintainer's perspective, it's a bug if the program disagrees with RFCs or it's documentation. From the user's perspective, it's a bug if the progra

Bug#265128: polipo: Here's another example

2005-01-13 Thread Greg Kochanski
Tom Huckstep wrote: On Wed, Jan 12, 2005 at 01:50:27AM +0100, Juliusz Chroboczek wrote: As you can see, both the Content-Type and Cache-Control headers are lacking the dash. According to the grammar in RFC 2616 Sections 4.2 and 2.2, a field name cannot contain a space. This is a bug in the server

Bug#265128: polipo: Here's another example

2005-01-12 Thread Tom Huckstep
On Wed, Jan 12, 2005 at 01:03:22PM +0100, Juliusz Chroboczek wrote: > > > Tom, could you please downgrade this bug report to ``wishlist''? > > > I'm not convinced it is wishlist, > > You're the maintainer, so it's up to you. > > (My argument is that normal and important imply it's a bug in Polip

Bug#265128: polipo: Here's another example

2005-01-12 Thread Juliusz Chroboczek
> > Tom, could you please downgrade this bug report to ``wishlist''? > I'm not convinced it is wishlist, You're the maintainer, so it's up to you. (My argument is that normal and important imply it's a bug in Polipo. I see this as a feature request, as the users are requesting that polipo shou

Bug#265128: polipo: Here's another example

2005-01-12 Thread Tom Huckstep
On Wed, Jan 12, 2005 at 01:50:27AM +0100, Juliusz Chroboczek wrote: > As you can see, both the Content-Type and Cache-Control headers are > lacking the dash. According to the grammar in RFC 2616 Sections 4.2 > and 2.2, a field name cannot contain a space. This is a bug in the > server (NS_3.0, wh

Bug#265128: polipo: Here's another example

2005-01-11 Thread Juliusz Chroboczek
> Here's the header information (from wget -s http://totale.usc.edu): Wget doesn't give you the right info; it's following a redirect to https://totale.usc.edu/, which speaks correct protocol. Using either telnet or curl -i, you can get at the original data: $ telnet totale.usc.edu 80 Trying