Closed
Bug 546616
Opened 15 years ago
Closed 15 years ago
Modify https.js to support web socket protocol or create a new server for the protocol
Categories
(Testing :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 570789
People
(Reporter: smaug, Unassigned)
References
(Depends on 1 open bug)
Details
Attachments
(1 file)
31.00 KB,
patch
|
Details | Diff | Splinter Review |
.
Comment 1•15 years ago
|
||
If you want, I can provide the hack I've done some time ago in the bug 472529, at <https://bugzilla.mozilla.org/attachment.cgi?id=380454&action=diff>. Then we could write mochitests for WebSockets.
In this mean while, someone else could setup an entire functional ws server, what do you think about?
Reporter | ||
Comment 2•15 years ago
|
||
(In reply to comment #1)
> If you want, I can provide the hack I've done some time ago in the bug 472529,
> at <https://bugzilla.mozilla.org/attachment.cgi?id=380454&action=diff>. Then we
> could write mochitests for WebSockets.
Having at least some tests for websockets is a must.
> In this mean while, someone else could setup an entire functional ws server,
> what do you think about?
That would be useful too, but it is even more critical to have automated tests.
For simple manual testing http://www.websockets.org/ might be good enough (if it works, haven't tried yet).
To test protocol handling there should be tests also for invalid frames and
binary frames etc.
Comment 3•15 years ago
|
||
It is my hack that makes httpd.js to support websockets. I've provided a very simple mochitest testing it. This patch should be applied on the last #472529 patch.
Wellington
Reporter | ||
Comment 4•15 years ago
|
||
Any help here would be great.
Reporter | ||
Comment 5•15 years ago
|
||
Jeff, would a patch like attachment 429815 [details] [diff] [review] be ok for httpd.js?
Comment 6•15 years ago
|
||
Is this attachment a diff on mozilla-central automation.py? Currently we have this setup to allow for dynamic web server and ports:
http://mxr.mozilla.org/mozilla-central/source/build/automation.py.in
Also on mozilla-central, we have changed localhost to be mochi.test:
https://elvis314.wordpress.com/2010/02/26/more-info-on-the-localhost-mochi-test-change/
Comment 7•15 years ago
|
||
(In reply to comment #6)
> Is this attachment a diff on mozilla-central automation.py? Currently we have
> this setup to allow for dynamic web server and ports:
> http://mxr.mozilla.org/mozilla-central/source/build/automation.py.in
Yes, it is too. I had to change it because I needed to bind the ws scheme in the tunnel that the sslproxy performs (even when not using ssl).
> Also on mozilla-central, we have changed localhost to be mochi.test:
> https://elvis314.wordpress.com/2010/02/26/more-info-on-the-localhost-mochi-test-change/
hmm, well, if you choose to use this patch for ws testing instead of forking httpd.js I can update.
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•7 years ago
|
Component: httpd.js → General
You need to log in
before you can comment on or make changes to this bug.
Description
•