This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section: http://www.whatwg.org/specs/web-apps/current-work/#attr-meta-http-equiv Comment: On http-state it was mentioned that browsers support Set-Cookie here. Ugh! Posted from: 58.1.224.28 by annevk@opera.com
http://www.google.com/codesearch?q=http-equiv%5Cs%2A%3D%5Cs%2A%28%22%7C%27%29%3Fset-cookie&hl=en&btnG=Search+Code
Adam, I expect I'll add this pragma as a non-conforming value that just invokes http-state's algorithms. Is there anything special I need to do to hand you a Unicode string representing a cookie, rather than a byte stream as provided by HTTP?
> Is there anything special I need to do to hand you a > Unicode string representing a cookie, rather than a byte stream as provided by > HTTP? Looks like it just calls through to setting document.cookie: http://trac.webkit.org/browser/trunk/WebCore/dom/Document.cpp#L2440 I think that means you'll eventually need to convert it back to bytes via UTF8.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments.
Checked in as WHATWG revision r5486. Check-in comment: Define http-equiv='set-cookie' http://html5.org/tools/web-apps-tracker?from=5485&to=5486