If onInputStreamReady doesn't process all of the Request-Line the first time, httpd.js asserts

RESOLVED FIXED

Status

Testing
General
RESOLVED FIXED
9 years ago
28 days ago

People

(Reporter: Waldo, Assigned: Waldo)

Tracking

({fixed1.9.1})

unspecified
fixed1.9.1
Points:
---
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

9 years ago
Created attachment 351918 [details] [diff] [review]
Patch and a couple tests
[Checkin: Comment 7]

I noticed this during an intermediate state in writing the first patch for bug 468087.  The browser usually spews the entire request at once, but in that case I mangled a Request-Line to be super-super-long, and it had to be split when the server got it, resulting in an assertion failure that the state at the start of _processHeaders was correct.  It's easy to verify patch correctness -- just look at the API docs for _processRequestLine!  :-)

This is a mistake from earlier iterations of the patch in bug 462864 when I hadn't quite grasped exactly what the meaning of the return value would be, for what it's worth.

(Ted says Core:Testing is dead, but it still seems the most accurate component for httpd.js bugs; the server's used in too many places to qualify for any one component in Testing, really.  A new component in Testing would be a great solution [and an even greater way to stroke own my ego!], but I don't think httpd.js bugs are quite common enough to warrant it.)
Attachment #351918 - Flags: review?(honzab.moz)
Attachment #351918 - Flags: review?(honzab.moz) → review+
Comment on attachment 351918 [details] [diff] [review]
Patch and a couple tests
[Checkin: Comment 7]

Oooops, I overlooked that... 

Is there any platform with MTU larger then 16k? CentOS 5.2 gives me 16436, Mac 10.4 about 8160, WinXP 1492. The blankline test could not be sufficient in some limit cases, probably raise from 13 to 14? 

Also, adding '[diff] unified=10' or so and hg 1.0.1 could help produce patches with larger context.
(Assignee)

Comment 2

9 years ago
Sure, I can raise it.  Frankly, as long as it trips *somewhere*, I'm not especially worried (cf. the constant 250 in the patch for bug 465921).

No worries about overlooking, either; I'm still probably the only person who really understands the entire server (although I hope someone could get to the same point if they really had to), and people I try to get up to speed on it are inevitably going to miss things occasionally.

Re context, I have it set up for diff that way but not for mq diffs, and I upload directly from .hg/patches.  I'm sure I've seen stuff about this in #hg at some point, but the flip was avoiding unnecessary conflicts as much as possible, and I'm unlikely to change that in the near future.
(Assignee)

Comment 3

9 years ago
Er, that should have been the constant 250 in bug 463254.
(Assignee)

Comment 4

9 years ago
Moving httpd.js bugs to the new Testing :: httpd.js component; filter out this bugmail by searching for "ICanHasHttpd.jsComponent".
Component: Testing → httpd.js
Product: Core → Testing
Version: Trunk → unspecified
(Assignee)

Comment 5

9 years ago
...and changing the QA contact as well.  Filter on the string "BugzillaQAContactHandlingIsStupid".
QA Contact: testing → httpd.js
(Assignee)

Comment 6

9 years ago
Fixed on trunk, waiting for tree to cycle to land on 191 to keep things sync'd, as this is test-only code and I'd like to avoid divergence while both are undergoing active development...
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Comment on attachment 351918 [details] [diff] [review]
Patch and a couple tests
[Checkin: Comment 7]

(In reply to comment #6)
> Fixed on trunk, waiting for tree to cycle to land on 191 to keep things sync'd,

http://hg.mozilla.org/mozilla-central/rev/469f2ddc1df5
http://hg.mozilla.org/releases/mozilla-1.9.1/rev/8c8869f150d2
Attachment #351918 - Attachment description: Patch and a couple tests → Patch and a couple tests [Checkin: Comment 7]
Keywords: fixed1.9.1
(Assignee)

Comment 8

9 years ago
Serge, please don't modify bug statuses and such things on my bugs when it's not clear I've completely forgotten about them.  In particular, it hasn't been that long since this was committed to 191, and I was still watching just to be sure nothing adverse was going to happen.
(Assignee)

Updated

9 years ago
Flags: in-testsuite+
(Assignee)

Comment 9

8 years ago
The changes to head_utils.js introduced a buglet that strangely doesn't result in test failures (or at least not enough for anyone to have reported it as a bug or pinged me).  See bug 508128 comment 59, to be fixed there fairly soon.
Component: httpd.js → General
Product: Testing → Testing
You need to log in before you can comment on or make changes to this bug.