Package: bugs.debian.org
Severity: normal


I was reviewing what passes for documentation on the use of usertags [1]
to query the bts, via bugs.debian.org/pkgreport.cgi, and started
experimenting in order to find what does & does not actually work,
inspired by the material in [2].

I put in this request:
http://bugs.debian.org/cgi-bin/[email protected];include=i386;

and got a 500 error.

I then put almost the same thing (removed the trailing ';')
http://bugs.debian.org/cgi-bin/[email protected];include=i386

and again got a 500 error.

The time stamps are
Sat 03 Oct 2009 11:06:01 GMT and
Sat 03 Oct 2009 11:06:04 GMT

So the first issue to report is the 500 errors, as the error message asks.
I may well be abusing the 'include' parameter but surely this could be
handled more gracefully.
I doubt my map{}-fu is up to writing a patch.


Then I noticed something a little odd which I should report too.
Perhaps it is just collateral damage from content negotiations.

In the first case, the output was formatted as plain text,
(ie the HTTP Content-Type:  header was text/plain)
while in the second it was normal HTML (text/html).
This behaviour doesn't seem to be entirely repeatable, but it
happened a few times at least. I expect one needs to clear browser
caches, etc first.

I tried the same urls with 'lynx -mime_header -source' and  got the
same output (text/plain) in both cases, apart from the HTTP Date: header
of course.

A related issue which I should perhaps file separately.
I also submitted this URL,
http://bugs.debian.org/cgi-bin/[email protected];include=alpha
at Sat 03 Oct 2009 11:28:18 GMT

and got _no output_ at all sent to the browser (iceweasel from 'etch'/i386).

I tried the same url with lynx and got the expected internal server error message, with Content-Type: text/plain.

Cheers
Vince

[1] http://wiki.debian.org/bugs.debian.org/usertags
[2] http://wiki.debian.org/DebianInstaller/Bugs



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to