Skip to main content

Browse the archive

Revision be26c4f22f52f4c488d8e9d586db50eea2428a10 authored by Jim Evans on 15 March 2018, 21:21:56 UTC, committed by Jim Evans on 15 March 2018, 21:21:56 UTC 
Editing expectations of domain attribute of returned cookie
 
For the domain attribute of a returned cookie, if the attribute value
conatains a domain with a single dot ('.'), some user agents prepend a
leading dot onto the beginning of the attribute value. This is consistent
with RFC 2965. Some user agents expressly omit the leading dot, which is
consistent with the later RFC 6265. This commit allows both values as the
returned value of the domain attribute.
1 parent 750cfaf
Raw File
nfc_recordType_opaque-manual.https.html 
<!DOCTYPE html>
<meta charset=utf-8>
<title>Web NFC Test: push and watch opaque records</title>
<link rel="author" title="Intel" href="http://www.intel.com"/>
<link rel="help" href="https://w3c.github.io/web-nfc/"/>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="resources/nfc_help.js"></script>
<meta name="flags" content="interact">
<meta name="timeout" content="long">

<p>Tap an NFC tag to the test device with NFC support.</p>

<p>Note: All the actions need to be done in 60 seconds, otherwise it will get TIMEOUT.</p>

<div id="log"></div>

<script>

"use strict";

setup({ explicit_timeout: true });

let desc = "Test that nfc.push and nfc.watch succeed when recordType is set to 'opaque'."
let watchOptions = {
  recordType : "opaque",
  mediaType : "application/octet-stream",
  url : ""
}
let message = createMessage([createOpaqueRecord(test_buffer_data)]);

testNFCMessage(message, watchOptions, desc);

</script>
back to top