Bug 63895 - EventSource.close() doesn't close an already open stream
Summary: EventSource.close() doesn't close an already open stream
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows 7
: P2 Major
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-04 02:23 PDT by Miloš Rašić
Modified: 2011-07-06 08:57 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Miloš Rašić 2011-07-04 02:23:14 PDT 
The bug occurs on WebKit version 533 as reported by jQuery on an Appcelerator Titanium Desktop application.

Calling close() method of an EventSource object doesn't close an already open text/event-stream connection. It correctly sets the readystate to 2 (CLOSED) and prevents EventSource object from making any further requests, but the already open connection remains open and the server has to be notified that it should close the connection from server side.
Comment 1 Miloš Rašić 2011-07-06 07:14:41 PDT 
It seems that this has been fixed in version 534. Just started testing my application on OS X today and Titanium Desktop for OS X reports webkit version 534.29. On this version, EventSource works as expected and closes the open connection when close() method is called.