Web Application Security Working Group - Activity in 2014
No matches.
TR publications
-
1 document published.
-
Requirements for Powerful Features published as a First Public Working Draft. History of Requirements for Powerful Features
-
Participants
-
1 participant left.
-
Devdatta Akhawe (W3C Invited Experts) left.
-
-
1 organization joined.
-
International Webmasters Association (IWA) joined.
-
GitHub
w3c/webappsec
-
8 issues opened.
-
Resolve ambiguity in the "parse metadata" algorithm between "()" and "no metadata" w3c/webappsec#119, by @fmarier.
-
Explicitly mention the four cases around the HTTPS requirement in SRI w3c/webappsec#116, by @fmarier.
-
[SRI] Inconsistent Integrity Metadata Conventions w3c/webappsec#114, by @lgarron.
-
Capability detection for referrer-policy? w3c/webappsec#113, by @hillbrad.
-
[CSP] Define encoding used for reports w3c/webappsec#111, by @hillbrad.
-
file URIs always fail integrity checks w3c/webappsec#106, by @mozfreddyb.
-
SRI: Comments on *Is resource eligible for integrity validation*, 3.3.2 w3c/webappsec#105, by @mozfreddyb.
-
normalize hash function algorithm name w3c/webappsec#104, by @mozfreddyb.
-
-
1 issue closed.
-
file URIs always fail integrity checks w3c/webappsec#106.
-
-
7 issues received 36 new comments.
-
Resolve ambiguity in the "parse metadata" algorithm between "()" and "no metadata" w3c/webappsec#119 (11 comments by @btoews, @devd, @fmarier)
-
[SRI] Inconsistent Integrity Metadata Conventions w3c/webappsec#114 (8 comments by @briansmith, @devd, @fmarier, @lgarron, @mikewest)
-
Explicitly mention the four cases around the HTTPS requirement in SRI w3c/webappsec#116 (7 comments by @devd, @fmarier, @mikewest)
-
SRI: remove integrity for downloads (for the minimum viable revision) w3c/webappsec#81 (3 comments by @hillbrad, @mozfreddyb)
-
[SRI]: use the terms of (un)authenticated origins instead of (in)secure channels? w3c/webappsec#71 (1 comment by @mozfreddyb)
-
-
12 pull requests opened.
-
Allow the empty set as a return value for parsemetada (fixes #119) w3c/webappsec#120, by @fmarier.
-
Move the fallback / noncanonical bits to v2 w3c/webappsec#118, by @fmarier.
-
Add a note about file URIs (fixes #106) w3c/webappsec#117, by @fmarier.
-
W3M reviewers suggest additional liasions w3c/webappsec#115, by @wseltzer.
-
Reset links to their original color w3c/webappsec#112, by @astorije.
-
clarify requirements for assistive technologies w3c/webappsec#110, by @hillbrad.
-
Update dependencies in webappsec-charter-2015.html w3c/webappsec#109, by @wseltzer.
-
`Authorization` is the header likely to be seen, not `WWW-Authenticate` w3c/webappsec#108, by @fmarier.
-
constrain the scope of the permissions API w3c/webappsec#107, by @hillbrad.
-
editorial updates w3c/webappsec#103, by @wseltzer.
-
draft note for interaction of sandbox directive and workers w3c/webappsec#102, by @hillbrad.
-
CSP: message-src and message-sink w3c/webappsec#101, by @deian.
-
-
12 pull requests merged.
-
Add a note about file URIs (fixes #106) w3c/webappsec#117.
-
`Authorization` is the header likely to be seen, not `WWW-Authenticate` w3c/webappsec#108.
-
W3M reviewers suggest additional liasions w3c/webappsec#115.
-
Reset links to their original color w3c/webappsec#112.
-
clarify requirements for assistive technologies w3c/webappsec#110.
-
Update dependencies in webappsec-charter-2015.html w3c/webappsec#109.
-
constrain the scope of the permissions API w3c/webappsec#107.
-
Label the three components of metadata w3c/webappsec#97.
-
Remove more unnecessary steps w3c/webappsec#96.
-
Remove trailing equal signs from the sha-512 examples w3c/webappsec#89.
-
Fix sha-256 hash name in example w3c/webappsec#78.
-
editorial updates w3c/webappsec#103.
-
-
10 pull requests received 11 new comments.
-
`Authorization` is the header likely to be seen, not `WWW-Authenticate` w3c/webappsec#108 (2 comments by @devd, @fmarier)
-
Allow the empty set as a return value for parsemetada (fixes #119) w3c/webappsec#120 (1 comment by @fmarier)
-
Mention the one thing that integrity protects against on insecure origins w3c/webappsec#98 (1 comment by @mozfreddyb)
-
Move hyperlink auditing ("ping") to the connect-src directive w3c/webappsec#99 (1 comment by @mikewest)
-
w3c/permissions
-
1 issue received 1 new comment.
TR publications
-
1 document published.
-
Mixed Content published as a Last Call Working Draft. History of Mixed Content
-
Participants
-
1 organization left.
-
Rochester Institute of Technology left.
-
GitHub
w3c/webappsec
-
13 issues opened.
-
csp spec doesn't compile w3c/webappsec#100, by @deian.
-
SHA256 mismatches w3c/webappsec#82, by @kravietz.
-
SRI: remove integrity for downloads (for the minimum viable revision) w3c/webappsec#81, by @mozfreddyb.
-
What's a sensible default for `manifest-src`? w3c/webappsec#80, by @marcoscaceres.
-
default-src should also set for manifest-src? w3c/webappsec#79, by @marcoscaceres.
-
update README.markdown w3c/webappsec#77, by @jht5945.
-
Overview.html syntax error? w3c/webappsec#76, by @jht5945.
-
SRI: Integration to Worker constructor seems brittle and not very future proof w3c/webappsec#75, by @mozfreddyb.
-
SRI: Add SHA-384 to the mandatory requirements? w3c/webappsec#72, by @mozfreddyb.
-
[SRI]: use the terms of (un)authenticated origins instead of (in)secure channels? w3c/webappsec#71, by @mozfreddyb.
-
CSP Sec 5.1 Worker owner document clarification w3c/webappsec#70, by @deian.
-
Clarification of CSP sandbox and workers. w3c/webappsec#69, by @deian.
-
-
5 issues closed.
-
Clarification of CSP sandbox and workers. w3c/webappsec#69.
-
default-src should also set for manifest-src? w3c/webappsec#79.
-
What's a sensible default for `manifest-src`? w3c/webappsec#80.
-
update README.markdown w3c/webappsec#77.
-
SRI: Add SHA-384 to the mandatory requirements? w3c/webappsec#72.
-
-
9 issues received 21 new comments.
-
What's a sensible default for `manifest-src`? w3c/webappsec#80 (5 comments by @hillbrad, @marcoscaceres)
-
SRI: Integration to Worker constructor seems brittle and not very future proof w3c/webappsec#75 (4 comments by @annevk, @mikewest, @mozfreddyb)
-
SRI: remove integrity for downloads (for the minimum viable revision) w3c/webappsec#81 (2 comments by @devd, @mozfreddyb)
-
SRI: Why do we strip trailing equal signs when "applying the algorithm to the resource" (3.3.1) w3c/webappsec#73 (2 comments by @devd, @mozfreddyb)
-
[SRI]: use the terms of (un)authenticated origins instead of (in)secure channels? w3c/webappsec#71 (1 comment by @mikewest)
-
-
19 pull requests opened.
-
Move hyperlink auditing ("ping") to the connect-src directive w3c/webappsec#99, by @fmarier.
-
Mention the one thing that integrity protects against on insecure origins w3c/webappsec#98, by @fmarier.
-
Label the three components of metadata w3c/webappsec#97, by @fmarier.
-
Remove more unnecessary steps w3c/webappsec#96, by @fmarier.
-
Hillbrad/pow less snark w3c/webappsec#95, by @hillbrad.
-
minor grammatical fixes w3c/webappsec#94, by @hillbrad.
-
merging into gh-pages w3c/webappsec#93, by @mozfreddyb.
-
re-building HTML from spec.markdown w3c/webappsec#92, by @mozfreddyb.
-
Expand on some topics in the body. w3c/webappsec#91, by @noncombatant.
-
Make the abstract more clear. w3c/webappsec#90, by @noncombatant.
-
Remove trailing equal signs from the sha-512 examples w3c/webappsec#89, by @fmarier.
-
Fixed mixed content issues in charter doc w3c/webappsec#88, by @pfreitag.
-
Update gh-pages. w3c/webappsec#87, by @mikewest.
-
Make the return value of "Parse metadata" consistent w3c/webappsec#86, by @fmarier.
-
SRI: Remove unnecessary step in "Apply algorithm to resource" w3c/webappsec#85, by @fmarier.
-
Fix the sed filtering to strip trailing equal signs w3c/webappsec#84, by @fmarier.
-
Added manifest-src to default-src list (closes #79) w3c/webappsec#83, by @marcoscaceres.
-
Fix sha-256 hash name in example w3c/webappsec#78, by @josh.
-
SRI: towards minimum viable SRI w3c/webappsec#74, by @mozfreddyb.
-
-
12 pull requests merged.
-
minor grammatical fixes w3c/webappsec#94.
-
Hillbrad/pow less snark w3c/webappsec#95.
-
merging into gh-pages w3c/webappsec#93.
-
re-building HTML from spec.markdown w3c/webappsec#92.
-
Expand on some topics in the body. w3c/webappsec#91.
-
Make the abstract more clear. w3c/webappsec#90.
-
Fixed mixed content issues in charter doc w3c/webappsec#88.
-
Update gh-pages. w3c/webappsec#87.
-
SRI: Remove unnecessary step in "Apply algorithm to resource" w3c/webappsec#85.
-
Added manifest-src to default-src list (closes #79) w3c/webappsec#83.
-
Fix the sed filtering to strip trailing equal signs w3c/webappsec#84.
-
SRI: towards minimum viable SRI w3c/webappsec#74.
-
-
1 pull request reopened.
-
Remove trailing equal signs from the sha-512 examples w3c/webappsec#89, by @fmarier.
-
-
7 pull requests received 25 new comments.
-
SRI: towards minimum viable SRI w3c/webappsec#74 (10 comments by @devd, @joelweinberger, @mikewest, @mozfreddyb)
-
Remove trailing equal signs from the sha-512 examples w3c/webappsec#89 (5 comments by @fmarier, @mozfreddyb)
-
Fix sha-256 hash name in example w3c/webappsec#78 (4 comments by @devd, @josh, @mikewest, @mozfreddyb)
-
SRI: Remove unnecessary step in "Apply algorithm to resource" w3c/webappsec#85 (3 comments by @devd, @mozfreddyb)
-
w3c/permissions
-
4 issues opened.
-
A "dismissed" state w3c/permissions#4, by @marcoscaceres.
-
Permission states w3c/permissions#3, by @marcoscaceres.
-
Redundant assertion w3c/permissions#2, by @marcoscaceres.
-
Add link to Moz's bugzilla bug to track this w3c/permissions#1, by @marcoscaceres.
-
-
1 issue closed.
-
Add link to Moz's bugzilla bug to track this w3c/permissions#1.
-
Participants
-
4 organizations joined.
-
Stanford University joined.
-
Tencent joined.
-
Meta joined.
-
Yandex joined.
-
GitHub
w3c/webappsec
-
5 issues opened.
-
SRI: noncanonical-src use cases w3c/webappsec#68, by @hillbrad.
-
Add frame-ancestors to directives ignored in meta w3c/webappsec#67, by @hillbrad.
-
[CSP] Specification misses an acknowledgment section w3c/webappsec#65, by @mozfreddyb.
-
[SRI] Caching implications w3c/webappsec#61, by @therazor.
-
-
4 issues closed.
-
[CSP] add a manifest-src (or similar) directive w3c/webappsec#29.
-
Add frame-ancestors to directives ignored in meta w3c/webappsec#67.
-
CSP: host-part does not account for IPv6 addresses w3c/webappsec#49.
-
[SRI] Caching implications w3c/webappsec#61.
-
-
3 issues received 3 new comments.
-
More clarification about which directives inherit the default-src value when not provided. w3c/webappsec#63 (1 comment by @mikewest)
-
3 pull requests opened.
-
Added support for web manifests (closes #29) w3c/webappsec#66, by @marcoscaceres.
-
Fix old digest attribute w3c/webappsec#62, by @josh.
-
-
3 pull requests merged.
-
Added support for web manifests (closes #29) w3c/webappsec#66.
-
Cleanup w3c/webappsec#64.
-
Fix old digest attribute w3c/webappsec#62.
-
-
2 pull requests received 7 new comments.
-
Added support for web manifests (closes #29) w3c/webappsec#66 (6 comments by @hillbrad, @marcoscaceres, @mikewest, @mounirlamouri)
-
TR publications
-
1 document published.
-
Mixed Content published as a Working Draft. History of Mixed Content
-
Participants
-
1 participant joined.
-
Jun Murai (W3C) joined.
-
-
2 organizations joined.
-
Verisign, Inc. joined.
-
Keio University joined.
-
-
1 organization left.
-
Cox Communications, Inc. left.
-
GitHub
w3c/webappsec
-
5 issues opened.
-
[MIX] private origin does not account for IPv6 w3c/webappsec#60, by @tomrittervg.
-
SRI: fix HTTP reference w3c/webappsec#55, by @reschke.
-
Incomplete sentence in CR draft, changes from 1.0 w3c/webappsec#53, by @hillbrad.
-
CSP reports for eval() and inline script are identical w3c/webappsec#52, by @kravietz.
-
[CSP] style-src without unsafe-eval should also block `.selectorText` w3c/webappsec#50, by @mozfreddyb.
-
-
4 issues closed.
-
Incomplete sentence in CR draft, changes from 1.0 w3c/webappsec#53.
-
[CSP] style-src without unsafe-eval should also block `.selectorText` w3c/webappsec#50.
-
Add a "Changes since 1.0" section to CSP2. w3c/webappsec#45.
-
Drop the "CH-" bit of "CH-CSP". w3c/webappsec#46.
-
-
2 issues received 5 new comments.
-
CSP reports for eval() and inline script are identical w3c/webappsec#52 (4 comments by @devd, @kravietz, @mikewest, @oreoshake)
-
-
6 pull requests opened.
-
Minor Typos w3c/webappsec#59, by @tomrittervg.
-
SRI: update HTTP/1.1 references and tune terminology w3c/webappsec#58, by @reschke.
-
update HTTP/1.1 references and terminology w3c/webappsec#57, by @reschke.
-
update links from HTTPbis drafts to actual RFCs; terminology: "represent... w3c/webappsec#56, by @reschke.
-
Small typo fix: controling -> controlling w3c/webappsec#54, by @terriko.
-
fix #50: add 'parse a group of selectors' algorithm to block list w3c/webappsec#51, by @mozfreddyb.
-
-
4 pull requests merged.
-
Minor Typos w3c/webappsec#59.
-
SRI: update HTTP/1.1 references and tune terminology w3c/webappsec#58.
-
Small typo fix: controling -> controlling w3c/webappsec#54.
-
fix #50: add 'parse a group of selectors' algorithm to block list w3c/webappsec#51.
-
-
2 pull requests closed.
-
update HTTP/1.1 references and terminology w3c/webappsec#57.
-
-
5 pull requests received 12 new comments.
-
update HTTP/1.1 references and terminology w3c/webappsec#57 (8 comments by @mikewest, @mnot, @reschke)
-
fix #50: add 'parse a group of selectors' algorithm to block list w3c/webappsec#51 (1 comment by @mikewest)
-
TR publications
-
1 document published.
-
Referrer Policy published as a First Public Working Draft. History of Referrer Policy
-
GitHub
w3c/webappsec
-
7 issues opened.
-
CSP: host-part does not account for IPv6 addresses w3c/webappsec#49, by @Rob--W.
-
[MIX] typo? spec says image is blockable request context w3c/webappsec#48, by @zcorpan.
-
Drop the "CH-" bit of "CH-CSP". w3c/webappsec#46, by @mikewest.
-
Add a "Changes since 1.0" section to CSP2. w3c/webappsec#45, by @mikewest.
-
Consider a directive to set `nosniff` policy for a document's resources. w3c/webappsec#44, by @mikewest.
-
[CSP] Unmatched paren w3c/webappsec#42, by @garrettr.
-
Define a term that should guard access to "Powerful New Features" w3c/webappsec#41, by @jyasskin.
-
-
2 issues closed.
-
[MIX] typo? spec says image is blockable request context w3c/webappsec#48.
-
[CSP] Unmatched paren w3c/webappsec#42.
-
-
4 issues received 8 new comments.
-
Define a term that should guard access to "Powerful New Features" w3c/webappsec#41 (5 comments by @annevk, @mikewest)
-
-
2 pull requests opened.
-
CSP: port-part may have multiple digits w3c/webappsec#47, by @Rob--W.
-
sandbox-token grammar modified w3c/webappsec#43, by @StefanOssendorf.
-
-
2 pull requests closed.
-
CSP: port-part may have multiple digits w3c/webappsec#47.
-
sandbox-token grammar modified w3c/webappsec#43.
-
-
2 pull requests received 2 new comments.
TR publications
-
2 documents published.
-
Content Security Policy Level 2 published as a Last Call Working Draft. History of Content Security Policy Level 2
-
Mixed Content published as a First Public Working Draft. History of Mixed Content
-
GitHub
w3c/webappsec
-
3 issues opened.
-
Is protocol upgrade Cross-Origin for purpose of Origin When Cross-Origin? w3c/webappsec#39, by @hillbrad.
-
Add informative reference for "object-capability discipline" w3c/webappsec#37, by @hillbrad.
-
-
3 issues closed.
-
Add informative reference for "object-capability discipline" w3c/webappsec#37.
-
3 issues received 10 new comments.
-
Is protocol upgrade Cross-Origin for purpose of Origin When Cross-Origin? w3c/webappsec#39 (5 comments by @jeisinger, @mikewest)
-
Add informative reference for "object-capability discipline" w3c/webappsec#37 (3 comments by @jeisinger, @mikewest)
-
Not clear that Origin Only and Origin when Cross-Origin are also None When Downgrade w3c/webappsec#38 (2 comments by @jeisinger)
-
-
2 pull requests opened.
-
Use `hash-value` instead of `base64-value` w3c/webappsec#40, by @jyasskin.
-
Omitted word: request w3c/webappsec#36, by @tyoshino.
-
-
3 pull requests merged.
-
Use `hash-value` instead of `base64-value` w3c/webappsec#40.
-
Omitted word: request w3c/webappsec#36.
-
CSP: Some editorial w3c/webappsec#35.
-
-
3 pull requests received 3 new comments.
GitHub
w3c/webappsec
-
4 issues received 8 new comments.
-
[CSP] add a manifest-src (or similar) directive w3c/webappsec#29 (4 comments by @marcoscaceres, @mikewest)
-
-
4 pull requests opened.
-
CSP: Some editorial w3c/webappsec#35, by @wwumit.
-
Push referrer to GitHub Pages w3c/webappsec#34, by @mikewest.
-
Initial draft for referrer policy w3c/webappsec#33, by @jeisinger.
-
CSP: Block redirects by default, introduce 'unsafe-redirect'. w3c/webappsec#32, by @mikewest.
-
-
3 pull requests merged.
-
Push referrer to GitHub Pages w3c/webappsec#34.
-
Initial draft for referrer policy w3c/webappsec#33.
-
CSP: Block redirects by default, introduce 'unsafe-redirect'. w3c/webappsec#32.
-
-
1 pull request received 1 new comment.
-
CSP: Block redirects by default, introduce 'unsafe-redirect'. w3c/webappsec#32 (1 comment by @mikewest)
-
Participants
-
2 organizations joined.
-
Mitsubishi Electric Corporation joined.
-
Verizon joined.
-
GitHub
w3c/webappsec
-
9 issues opened.
-
[CSP] add a manifest-src (or similar) directive w3c/webappsec#29, by @marcoscaceres.
-
[CSP] Authors SHOULD sounds weird w3c/webappsec#28, by @marcoscaceres.
-
[CSP] Authors SHOULD sounds weird w3c/webappsec#27, by @marcoscaceres.
-
[CSP] Avoid RFC2119 keywords in non-normative sections w3c/webappsec#26, by @marcoscaceres.
-
[CSP] Server is not a valid conforming class of product w3c/webappsec#25, by @marcoscaceres.
-
[CSP] Delivery... should it mention meta? w3c/webappsec#24, by @marcoscaceres.
-
[csp] show how server is contacted with `Content-Security-Policy-Report-Only` w3c/webappsec#23, by @marcoscaceres.
-
[csp] References are out of date w3c/webappsec#22, by @marcoscaceres.
-
[CSP] Note about "Content-Security-Policy-Report-Only" w3c/webappsec#21, by @marcoscaceres.
-
-
6 issues closed.
-
[CSP] Authors SHOULD sounds weird w3c/webappsec#28.
-
[CSP] Authors SHOULD sounds weird w3c/webappsec#27.
-
[CSP] Note about "Content-Security-Policy-Report-Only" w3c/webappsec#21.
-
[CSP] Delivery... should it mention meta? w3c/webappsec#24.
-
-
1 issue reopened.
-
[subresource-integrity] With proxies, no-transform should be (at least) should w3c/webappsec#14, by @devd.
-
-
5 issues received 8 new comments.
-
[CSP] Avoid RFC2119 keywords in non-normative sections w3c/webappsec#26 (2 comments by @marcoscaceres, @mikewest)
-
[csp] show how server is contacted with `Content-Security-Policy-Report-Only` w3c/webappsec#23 (1 comment by @marcoscaceres)
-
-
5 pull requests opened.
-
Fix some minor typos w3c/webappsec#31, by @mathiasbynens.
-
MIX: Adding a draft mixed content spec. w3c/webappsec#30, by @mikewest.
-
A few typographical fixes for CSP 1.0 and 1.1 and also SRI w3c/webappsec#20, by @terriko.
-
CSP: Porting from Respec to Bikeshed. w3c/webappsec#19, by @mikewest.
-
CSP: Document proposed solution to redirect-target path leakage. w3c/webappsec#18, by @mikewest.
-
-
5 pull requests merged.
-
Fix some minor typos w3c/webappsec#31.
-
MIX: Adding a draft mixed content spec. w3c/webappsec#30.
-
CSP: Document proposed solution to redirect-target path leakage. w3c/webappsec#18.
-
A few typographical fixes for CSP 1.0 and 1.1 and also SRI w3c/webappsec#20.
-
CSP: Porting from Respec to Bikeshed. w3c/webappsec#19.
-
-
1 pull request received 3 new comments.
-
A few typographical fixes for CSP 1.0 and 1.1 and also SRI w3c/webappsec#20 (3 comments by @devd, @mikewest, @terriko)
-
Participants
-
1 organization joined.
-
Pacific Northwest National Laboratory joined.
-
GitHub
w3c/webappsec
-
2 issues opened.
-
[SRI] Talk about Fonts w3c/webappsec#17, by @devd.
-
SRI: Fine grained "require integrity" option w3c/webappsec#16, by @devd.
-
TR publications
-
2 documents published.
-
User Interface Security Directives for Content Security Policy published as a Last Call Working Draft. History of User Interface Security Directives for Content Security Policy
-
Subresource Integrity published as a First Public Working Draft. History of Subresource Integrity
-
GitHub
w3c/webappsec
-
6 issues opened.
-
SRI: Normatively reference Fetch. w3c/webappsec#15, by @mikewest.
-
[subresource-integrity] With proxies, no-transform should be (at least) should w3c/webappsec#14, by @yoavweiss.
-
SI: Iframe element integrity w3c/webappsec#9, by @mozfreddyb.
-
SI: Manual issue numbering. w3c/webappsec#7, by @mikewest.
-
SI: Change Accept Header w3c/webappsec#6, by @devd.
-
SI: Talk about Image Elements with srcset attributes w3c/webappsec#5, by @devd.
-
-
5 issues closed.
-
SRI: Normatively reference Fetch. w3c/webappsec#15.
-
SI: Iframe element integrity w3c/webappsec#9.
-
SI: Change Accept Header w3c/webappsec#6.
-
SI: Manual issue numbering. w3c/webappsec#7.
-
Subresource Integrity Length Extension? w3c/webappsec#3.
-
-
3 issues received 8 new comments.
-
[subresource-integrity] With proxies, no-transform should be (at least) should w3c/webappsec#14 (5 comments by @devd, @mikewest, @mozfreddyb)
-
-
5 pull requests opened.
-
Some grammar fixes w3c/webappsec#13, by @wseltzer.
-
set shortname to 'subint' w3c/webappsec#12, by @hillbrad.
-
Added language about GUID URI schemes. w3c/webappsec#10, by @hillbrad.
-
SI: Set 'Accept' header to the integrity metadata's content type. (bug #6) w3c/webappsec#8, by @mikewest.
-
-
4 pull requests merged.
-
Some grammar fixes w3c/webappsec#13.
-
Added language about GUID URI schemes. w3c/webappsec#10.
-
1 pull request closed.
-
set shortname to 'subint' w3c/webappsec#12.
-
-
3 pull requests received 6 new comments.
-
SI: Set 'Accept' header to the integrity metadata's content type. (bug #6) w3c/webappsec#8 (3 comments by @mikewest, @mozfreddyb)
-
adding an explicit note that integrity verification stops at an iframe's document source w3c/webappsec#11 (1 comment by @mikewest)
-
TR publications
-
1 document published.
-
Content Security Policy 1.1 published as a Working Draft. History of Content Security Policy 1.1
-
Participants
-
1 organization left.
-
Mobile Web Forum left.
-
GitHub
w3c/webappsec
-
1 pull request opened.
-
Added relation to XFO header. w3c/webappsec#4, by @hillbrad.
-
-
1 pull request merged.
-
Added relation to XFO header. w3c/webappsec#4.
-
-
1 pull request received 1 new comment.
TR publications
-
1 document published.
-
Cross-Origin Resource Sharing published as a Recommendation. History of Cross-Origin Resource Sharing
-
GitHub
w3c/webappsec
-
1 issue opened.
-
Subresource Integrity Length Extension? w3c/webappsec#3, by @nlyan2025.
-
-
1 issue received 4 new comments.
-
Subresource Integrity Length Extension? w3c/webappsec#3 (4 comments by @devd, @hillbrad, @mikewest, @nlyan2025)
-
-
2 pull requests opened.
-
update sandbox flag list w3c/webappsec#2, by @deian.
-
Added frame-ancestors directive. w3c/webappsec#1, by @hillbrad.
-
-
2 pull requests merged.
-
update sandbox flag list w3c/webappsec#2.
-
Added frame-ancestors directive. w3c/webappsec#1.
-
-
1 pull request received 1 new comment.