Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update (most) tables to be md compatible in Web/HTTP #7815

Merged
merged 2 commits into from
Aug 12, 2021
Merged

Update (most) tables to be md compatible in Web/HTTP #7815

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9a63cc4
Update tables to be md compatible in Web/HTTP
teoli2003 Aug 11, 2021
3c65a01
Fix text/javascript
teoli2003 Aug 12, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 5 additions & 11 deletions files/en-us/web/http/basics_of_http/mime_types/common_types/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,12 +27,12 @@

<p>IANA is the official registry of MIME media types and maintains a <a href="https://www.iana.org/assignments/media-types/media-types.xhtml">list of all the official MIME types</a>. This table lists some important MIME types for the Web:</p>

<table class="standard-table">
<table>
<thead>
<tr>
<th scope="col">Extension</th>
<th scope="col">Kind of document</th>
<th scope="col">MIME Type</th>
<th>Extension</th>
<th>Kind of document</th>
<th>MIME Type</th>
</tr>
</thead>
<tbody>
Expand Down Expand Up @@ -162,13 +162,7 @@
<td><code>.js</code></td>
<td>JavaScript</td>
<td>
<p><code>text/javascript</code>, per the following specifications:</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, this was added here because we had several issues changing it back and forth. See #4077. Can we leave this here somehow?


<ul>
<li><a href="https://html.spec.whatwg.org/multipage/#scriptingLanguages">https://html.spec.whatwg.org/multipage/#scriptingLanguages</a></li>
<li><a href="https://html.spec.whatwg.org/multipage/#dependencies:willful-violation">https://html.spec.whatwg.org/multipage/#dependencies:willful-violation</a></li>
<li><a href="https://datatracker.ietf.org/doc/draft-ietf-dispatch-javascript-mjs/">https://datatracker.ietf.org/doc/draft-ietf-dispatch-javascript-mjs/</a></li>
</ul>
<code>text/javascript</code> (Specifications: <a href="https://html.spec.whatwg.org/multipage/#scriptingLanguages">HTML</a> and its <a href="https://html.spec.whatwg.org/multipage/#dependencies:willful-violation">reasoning</a>, and <a href="https://datatracker.ietf.org/doc/draft-ietf-dispatch-javascript-mjs/">IETF</a>)
</td>
</tr>
<tr>
Expand Down
42 changes: 19 additions & 23 deletions files/en-us/web/http/csp/errors/cspviolation/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,32 +18,28 @@
---
<p>{{HTTPSidebar}}</p>

<p>The warning "Content Security Policy: The page’s settings blocked the loading of a resource: xyz" occurs when the page's CSP configuration given by <code>xyz</code> prevents the resource from being loaded into the document's context.</p>
<p>The warning "Content Security Policy: The page's settings blocked the loading of a resource: xyz" occurs when the page's CSP configuration given by <code>xyz</code> prevents the resource from being loaded into the document's context.</p>

<h2 id="Message">Message</h2>

<table class="standard-table">
<tbody>
<tr>
<th scope="row">Firefox</th>
<td><code>Content Security Policy: The page’s settings blocked the loading of a resource: <em>xyz</em></code></td>
</tr>
<tr>
<th rowspan="4" scope="row">Chrome</th>
<td><code>Refused to apply inline style because it violates the following Content Security Policy Directive: "<em>xyz</em>". <em>uvw</em>.</code></td>
</tr>
<tr>
<td><code>Refused to execute inline script because it violates the following Content Security Policy directive: "<em>xyz</em>". <em>uvw</em>.</code></td>
</tr>
<tr>
<td><code>Refused to run the JavaScript URL because it violates the following Content Security Policy directive: "<em>xyz</em>". <em>uvw</em>.</code></td>
</tr>
<tr>
<td><code>Refused to execute inline event handler because it violates the following Content Security Policy directive: "<em>xyz</em>". <em>uvw</em>.</code></td>
</tr>
</tbody>
</table>
<h3>Firefox</h3>
<p><code>Content Security Policy: The pages settings blocked the loading of a resource: <em>xyz</em></code></p>
</p>with:</p>
<dl>
<dt><code>xyz</code></dt>
<dd>The name of the CSP directive that blocked the resource. This may be expressed as either just the name of the directive, or as the entire policy directive string.</dd>
<dt><code>uvw</code></dt>
<dd>Text that provides information that may help you resolve the problem, potentially including specific changes you might make to the CSP configuration.</dd>
</dl>

<h3>Chrome</h3>
<ul>
<li><code>Refused to apply inline style because it violates the following Content Security Policy Directive: "<em>xyz</em>". <em>uvw</em>.</code></li>
<li><code>Refused to execute inline script because it violates the following Content Security Policy directive: "<em>xyz</em>". <em>uvw</em>.</code></li>
<li><code>Refused to run the JavaScript URL because it violates the following Content Security Policy directive: "<em>xyz</em>". <em>uvw</em>.</code></li>
<li><code>Refused to execute inline event handler because it violates the following Content Security Policy directive: "<em>xyz</em>". <em>uvw</em>.</code></li>
</ul>
<p>with:</p>
<dl>
<dt><code>xyz</code></dt>
<dd>The name of the CSP directive that blocked the resource. This may be expressed as either just the name of the directive, or as the entire policy directive string.</dd>
Expand All @@ -62,7 +58,7 @@ <h2 id="What_went_wrong">What went wrong?</h2>
<h2 id="See_also">See also</h2>

<ul>
<li><a href="/en-US/docs/Web/HTTP/CSP/Errors">CSP errors and warnings</a></li>
<li><a href="/en-US/docs/Web/HTTP/CSP/Errors">CSP errors and warnings</a></li>
<li><a href="/en-US/docs/Web/HTTP/CSP">Content Security Policy</a></li>
<li>{{HTTPHeader("Content-Security-Policy")}}</li>
<li>{{HTTPHeader("Content-Security-Policy-Report-Only")}}</li>
Expand Down
57 changes: 23 additions & 34 deletions files/en-us/web/http/headers/digest/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,22 +11,21 @@
<p>The <code><strong>Digest</strong></code> response HTTP header provides a
{{Glossary("digest")}} of the requested resource.</p>

<p>In <a href="https://datatracker.ietf.org/doc/html/rfc7231">RFC 7231</a> terms this is the
<em>selected representation</em> of a resource. The selected representation depends on
the <code><a href="/en-US/docs/Web/HTTP/Headers/Content-Type">Content-Type</a></code>
and
<code><a href="/en-US/docs/Web/HTTP/Headers/Content-Encoding">Content-Encoding</a></code>
header values: so a single resource may have multiple different digest values.</p>
<p>
In <a href="https://datatracker.ietf.org/doc/html/rfc7231">RFC 7231</a> terms,
this is the <em>selected representation</em> of a resource.
The selected representation depends
on the <code><a href="/en-US/docs/Web/HTTP/Headers/Content-Type">Content-Type</a></code>
and <code><a href="/en-US/docs/Web/HTTP/Headers/Content-Encoding">Content-Encoding</a></code> header values,
so a single resource may have multiple different digest values.
</p>

<p>The digest is calculated over the entire representation. The representation itself may
be:</p>
<p>The digest is calculated over the entire representation. The representation itself may be:</p>

<ul>
<li>fully contained in the response message body</li>
<li>not at all contained in the message body (for example, in a response to a
<code><a href="/en-US/docs/Web/HTTP/Methods/HEAD">HEAD</a></code> request)</li>
<li>partially contained in the message body (for example, in a response to a <a
href="/en-US/docs/Web/HTTP/Range_requests">range request</a>).</li>
<li>fully contained in the response message body,</li>
<li>not at all contained in the message body (for example, in a response to a <code><a href="/en-US/docs/Web/HTTP/Methods/HEAD">HEAD</a></code> request),</li>
<li>or partially contained in the message body (for example, in a response to a <a href="/en-US/docs/Web/HTTP/Range_requests">range request</a>).</li>
</ul>

<table class="properties">
Expand All @@ -44,8 +43,7 @@

<h2 id="Syntax">Syntax</h2>

<pre class="brush: html">Digest: &lt;digest-algorithm&gt;=&lt;digest-value&gt;

<pre>Digest: &lt;digest-algorithm&gt;=&lt;digest-value&gt;
Digest: &lt;digest-algorithm&gt;=&lt;digest-value&gt;,&lt;digest-algorithm&gt;=&lt;digest-value&gt;
</pre>

Expand All @@ -67,35 +65,26 @@ <h2 id="Directives">Directives</h2>

<h2 id="Examples">Examples</h2>

<pre class="brush: html">Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=
<pre>Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=
Digest: sha-256=X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=,unixsum=30637</pre>

<h2 id="Specifications">Specifications</h2>

<table class="standard-table">
<thead>
<table>
<tr>
<th scope="col">Specification</th>
<th scope="col">Title</th>
<th>Specification</th>
</tr>
</thead>
<tbody>
<tr>
<td>
<p><a href="https://datatracker.ietf.org/doc/draft-ietf-httpbis-digest-headers">draft-ietf-httpbis-digest-headers-latest</a>
</p>
</td>
<td>Resource Digests for HTTP</td>
<td><a href="https://datatracker.ietf.org/doc/draft-ietf-httpbis-digest-headers">draft-ietf-httpbis-digest-headers-latest</a></td>
</tr>
</tbody>
</table>

<p>This header was originally defined in <a href="https://datatracker.ietf.org/doc/html/rfc3230">RFC
3230</a>, but the definition of "selected representation" in <a
href="https://www.rfc-editor.org/info/rfc7231">RFC 7231</a> made the original
definition inconsistent with current HTTP specifications. When released, The "Resource
Digests for HTTP" draft therefore will obsolete RFC 3230 and will update the standard to
be consistent.</p>
<p>
This header was originally defined in <a href="https://datatracker.ietf.org/doc/html/rfc3230">RFC 3230</a>,
but the definition of "selected representation" in <a href="https://www.rfc-editor.org/info/rfc7231">RFC 7231</a> made the original definition inconsistent with current HTTP specifications.
When released, The "Resource Digests for HTTP" draft therefore will obsolete RFC 3230
and will update the standard to be consistent.
</p>

<h2 id="Browser_compatibility">Browser compatibility</h2>

Expand Down
Loading