Closed
Bug 300050
Opened 19 years ago
Closed 19 years ago
SOAP requests do not return cookies
Categories
(Core Graveyard :: Web Services, defect)
Core Graveyard
Web Services
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: Dave, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4 SOAP requests do not return cookies when either the cookie was already set for the SOAP URI or when included in the HTTP headers of a SOAP response. The demonstrating URL above is the lead-in page for a SOAP demo program. The application server attempts to set a cookie named "BISKit" to identify further requests (that return the cookie). Since the cookie is not returned for SOAP requests, each response sets a new value for this cookie. Reproducible: Always Steps to Reproduce: 1. Go to the demonstration URL and run the demo. 2. Monitor the HTTP headers and note that the BISKit cookie is never returned with SOAP requests and changes value in every response. Actual Results: No cookie is returned in the HTTP headers of SOAP requests even though a cookie is set for the root directory of the server. Note that the demo is written to not depend on the cookie being returned, so it still works even though a new application server instance must be started for every request. Expected Results: Applicable cookies should be returned in the HTTP headers just as they are for any other HTTP-based request. Tried on both Linux (Fedora Core 3) and Windows XP with Firefox 1.04 with the same results.
->Core: Web Services
Assignee: nobody → web-services
Component: General → Web Services
Product: Firefox → Core
QA Contact: general → doronr
Version: unspecified → Trunk
Reporter | ||
Comment 2•19 years ago
|
||
URL is no longer valid but the problem persists.
Reporter | ||
Comment 3•19 years ago
|
||
Not a problem in 1.0.7 and later.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 4•19 years ago
|
||
No specific bug / patch referenced as the fix. -> WORKSFORME
Updated•19 years ago
|
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Updated•19 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → WORKSFORME
Updated•7 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•