file stringlengths 16 94 | text stringlengths 32 24.4k | vector list |
|---|---|---|
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Response Directives - `s-maxage`:
The `s-maxage` response directive indicates how long the response remains fresh in a shared cache. The `s-maxage` directive is ignored by private caches, and overrides the value specified by the `max-age` directive or the `Expires` header ... | [
-0.6043899655342102,
-0.7085561752319336,
-1.988988995552063,
-0.38019880652427673,
-1.0838408470153809,
-2.2139453887939453,
1.0762945413589478,
1.5284491777420044,
-0.30944037437438965,
-0.2188534289598465,
0.043140217661857605,
0.27698633074760437,
-0.3476344048976898,
0.477548897266387... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Response Directives - `no-cache`:
The `no-cache` response directive indicates that the response can be stored in caches, but the response must be validated with the origin server before each reuse, even when the cache is disconnected from the origin server.
Example:
Cach... | [
1.031104564666748,
-0.26226651668548584,
-0.06312142312526703,
0.5284011363983154,
1.0072308778762817,
-1.1822259426116943,
0.81351238489151,
1.6182044744491577,
-0.9602734446525574,
-0.03484435752034187,
0.13642220199108124,
0.6577333807945251,
-0.17111890017986298,
0.6577935814857483,
... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Response Directives - `proxy-revalidate`:
The `proxy-revalidate` response directive is the equivalent of `must-revalidate`, but specifically for shared caches only. | [
-0.4184234142303467,
0.2086687535047531,
-1.1143912076950073,
-0.4506843090057373,
-0.5333348512649536,
-0.8657953143119812,
1.050744652748108,
1.4687635898590088,
-0.20782995223999023,
0.8002011775970459,
-0.8439592719078064,
-0.9893628358840942,
-0.38637059926986694,
0.8111776113510132,
... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Response Directives - `no-store`:
The `no-store` response directive indicates that any caches of any kind (private or shared) should not store this response.
Example:
Cache-Control: no-store | [
0.0009568090317770839,
-0.5609107613563538,
-1.042649745941162,
0.11139741539955139,
-1.2623224258422852,
-1.3486055135726929,
-0.3546350300312042,
1.4512735605239868,
0.0017910078167915344,
-0.056555673480033875,
0.2788378894329071,
-0.47521382570266724,
-0.6598847508430481,
0.08087299764... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Response Directives - `private`:
The `private` response directive indicates that the response can be stored only in a private cache (e.g., local caches in browsers).
Example:
Cache-Control: private
You should add the `private` directive for user-personalized content, es... | [
-0.7767438292503357,
-0.16167891025543213,
-1.2561360597610474,
-0.03442525863647461,
-0.5691334009170532,
-1.4601788520812988,
1.0919338464736938,
0.8617722392082214,
-0.274969220161438,
-0.4164961576461792,
-0.3026231825351715,
-0.2888362407684326,
-0.7035972476005554,
0.1073986291885376... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Response Directives - `public`:
The `public` response directive indicates that the response can be stored in a shared cache. Responses for requests with `Authorization` header fields must not be stored in a shared cache; however, the `public` directive will cause such resp... | [
1.2864818572998047,
-0.8086487054824829,
-0.5985244512557983,
0.12578003108501434,
0.050343066453933716,
-1.8865073919296265,
0.432314395904541,
1.2380393743515015,
0.24321934580802917,
-0.4315038025379181,
-0.4503145217895508,
0.272470086812973,
-0.3228518068790436,
0.06858564913272858,
... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Response Directives - `must-understand`:
The `must-understand` response directive indicates that a cache should store the response only if it understands the requirements for caching based on status code.
`must-understand` should be coupled with `no-store` for fallback be... | [
0.17369873821735382,
-0.8333024382591248,
-0.5927079916000366,
-0.1992345005273819,
-0.7716013789176941,
-1.7761149406433105,
0.0252242349088192,
0.6321977972984314,
-0.2976377010345459,
0.644400417804718,
-0.7239540219306946,
-1.454484462738037,
-0.5729570984840393,
1.0719127655029297,
... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Response Directives - `no-transform`:
Some intermediaries transform content for various reasons. For example, some convert images to reduce transfer size. In some cases, this is undesirable for the content provider.
`no-transform` indicates that any intermediary (regardle... | [
-0.0642019659280777,
-0.5886741876602173,
-0.8480561971664429,
-0.6819890141487122,
-1.193910002708435,
-1.032223105430603,
-0.2653923034667969,
1.7381927967071533,
-0.390597403049469,
-0.1894710212945938,
0.038853637874126434,
-1.0477113723754883,
-1.1597654819488525,
-0.04506366699934006... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Response Directives - `immutable`:
The `immutable` response directive indicates that the response will not be updated while it's fresh.
Example:
Cache-Control: public, max-age=604800, immutable
A modern best practice for static resources is to include version/hashes in ... | [
-0.6819500923156738,
-0.255337119102478,
-0.9061121344566345,
-0.3957884907722473,
-0.6532347202301025,
-2.1138107776641846,
1.2083690166473389,
1.048591136932373,
0.043239571154117584,
0.14358939230442047,
-0.32267841696739197,
-0.044403593987226486,
-0.8784977793693542,
0.446576058864593... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Response Directives - `stale-while-revalidate`:
The `stale-while-revalidate` response directive indicates that the cache could reuse a stale response while it revalidates it to a cache.
Example:
Cache-Control: max-age=604800, stale-while-revalidate=86400
In the example ... | [
0.6418826580047607,
-0.38797613978385925,
-0.500687301158905,
0.07170895487070084,
0.03444463014602661,
-1.7618327140808105,
0.2612886130809784,
1.2684379816055298,
-0.051805317401885986,
0.10565821081399918,
-0.39509516954421997,
0.22387057542800903,
-0.19525733590126038,
0.67080575227737... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Response Directives - `stale-if-error`:
The `stale-if-error` response directive indicates that the cache can reuse a stale response when an upstream server generates an error, or when the error is generated locally. Here, an error is considered any response with a status c... | [
-0.4296948313713074,
-0.6291542053222656,
-1.124955415725708,
-0.037489280104637146,
-0.15726402401924133,
-1.98093581199646,
0.43799078464508057,
2.134443998336792,
-0.42758867144584656,
0.5939302444458008,
-0.04191053286194801,
-0.5122446417808533,
-0.24349182844161987,
0.964299678802490... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Request Directives - `no-cache`:
The `no-cache` request directive asks caches to validate the response with the origin server before reuse.
Example:
Cache-Control: no-cache
`no-cache` allows clients to request the most up-to-date response even if the cache has a fresh r... | [
-0.08694121241569519,
-0.14060379564762115,
-0.821704089641571,
-0.21263429522514343,
-1.1623531579971313,
-1.0812395811080933,
1.2155731916427612,
1.4237096309661865,
-1.0682106018066406,
0.25512242317199707,
0.08402886241674423,
-0.7576830387115479,
-0.14762264490127563,
0.62184077501297... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Request Directives - `no-store`:
The `no-store` request directive allows a client to request that caches refrain from storing the request and corresponding response — even if the origin server's response could be stored.
Example:
Cache-Control: no-store | [
0.0007527790148742497,
-0.4227348566055298,
-1.0288499593734741,
0.07195115089416504,
-0.7836498022079468,
-1.407485842704773,
-0.7126043438911438,
1.217799425125122,
-0.10424531251192093,
0.3488382399082184,
0.4871709942817688,
-0.7136073112487793,
-0.8500823378562927,
-0.1857498288154602... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Request Directives - `max-age`:
The `max-age=N` request directive indicates that the client allows a stored response that is generated on the origin server within N seconds — where N may be any non-negative integer (including `0`).
Example:
Cache-Control: max-age=10800
... | [
0.8752778172492981,
-0.9440652132034302,
-0.9030585885047913,
0.8024170994758606,
0.16750669479370117,
-1.3042454719543457,
0.18345828354358673,
1.6866856813430786,
-0.18184563517570496,
-0.25542977452278137,
-0.5117170810699463,
0.5618723034858704,
-0.028927909210324287,
0.062871932983398... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Request Directives - `max-stale`:
The `max-stale=N` request directive indicates that the client allows a stored response that is stale within N seconds. If no N value is specified, the client will accept a stale response of any age.
Example:
Cache-Control: max-stale=3600... | [
0.5428481101989746,
-0.9827256202697754,
-0.6245683431625366,
0.6478579044342041,
-0.22005131840705872,
-1.2809759378433228,
0.12267151474952698,
1.4003865718841553,
0.166158065199852,
-0.04264584556221962,
-0.26033854484558105,
0.29937881231307983,
0.022446371614933014,
0.0630774348974227... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Request Directives - `min-fresh`:
The `min-fresh=N` request directive indicates that the client allows a stored response that is fresh for at least N seconds.
Example:
Cache-Control: min-fresh=600
In the case above, if the response with `Cache-Control: max-age=3600` was... | [
-0.045627571642398834,
-0.5133447647094727,
-0.7249327301979065,
0.023601800203323364,
-0.8887442946434021,
-1.8989512920379639,
0.04123210906982422,
0.9368155002593994,
-0.20194125175476074,
0.0061422474682331085,
-0.05082976818084717,
-0.14479652047157288,
-0.39224472641944885,
1.0190753... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Request Directives - `no-transform`:
Same meaning that `no-transform` has for a response, but for a request instead. | [
0.12393569201231003,
-0.02674676477909088,
-0.7251762747764587,
-0.261385440826416,
-1.0737311840057373,
-1.8363850116729736,
0.2706663906574249,
1.638346791267395,
-0.08565380424261093,
-0.2873561978340149,
0.571111798286438,
-1.4841930866241455,
-0.8200909495353699,
-0.03559369593858719,... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Request Directives - `only-if-cached`:
The client indicates that an already-cached response should be returned. If a cache has a stored response, even a stale one, it will be returned. If no cached response is available, a 504 Gateway Timeout response will be returned. | [
-0.9247120022773743,
-0.15531349182128906,
-0.45841655135154724,
0.2994116544723511,
-0.40099796652793884,
-1.8818401098251343,
0.2939978241920471,
1.6861698627471924,
-1.0065401792526245,
0.40941670536994934,
0.095955029129982,
-0.7695775628089905,
-0.2718544006347656,
0.18374060094356537... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Directives - Request Directives - `stale-if-error`:
The `stale-if-error` request directive indicates that the browser is interested in receiving stale content on error from any intermediate server for a particular origin. This is not supported by any browser (see Browser compatibility)... | [
-0.34028059244155884,
-0.5143248438835144,
-1.127795696258545,
-0.010138439014554024,
-0.3087625503540039,
-1.0689656734466553,
0.5321584343910217,
1.1647095680236816,
-0.5964259505271912,
0.08609200268983841,
0.2888730466365814,
-1.5342031717300415,
-0.5305139422416687,
0.0436019599437713... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Use Cases - Preventing storing:
If you don't want a response stored in caches, use the `no-store` directive.
Example:
Cache-Control: no-store
Note that `no-cache` means "it can be stored but don't reuse before validating" — so it's not for preventing a response from being stored.
E... | [
1.0421819686889648,
-0.5080538988113403,
-0.10419915616512299,
0.31131914258003235,
-0.18302175402641296,
-1.187582015991211,
-0.4561193883419037,
1.1764732599258423,
-0.2983173727989197,
0.015548082999885082,
-0.7448593974113464,
-0.28105729818344116,
-0.24537374079227448,
0.8626875281333... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Use Cases - Caching static assets with "cache busting":
When you build static assets with versioning/hashing mechanisms, adding a version/hash to the filename or query string is a good way to manage caching.
For example:
Example:
<!-- index.html -->
<script src="/assets/react.min.js... | [
0.036870550364255905,
-0.5897104740142822,
-0.35943588614463806,
0.8912638425827026,
0.29104501008987427,
-1.6533595323562622,
0.38263779878616333,
1.4492908716201782,
-0.12128891795873642,
-0.21760593354701996,
-0.4550386667251587,
0.5705102682113647,
-0.874902606010437,
-0.05636658519506... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Use Cases - Up-to-date contents always:
For content that's generated dynamically, or that's static but updated often, you want a user to always receive the most up-to-date version.
If you don't add a `Cache-Control` header because the response is not intended to be cached, that could ... | [
0.9553888440132141,
-0.2804136574268341,
-0.5907999873161316,
1.2054892778396606,
0.1447363942861557,
-1.6448512077331543,
-0.11640805006027222,
1.4760640859603882,
0.04446439445018768,
0.15833452343940735,
-0.6977658867835999,
0.3417825698852539,
-0.42465364933013916,
0.046129487454891205... |
http/reference/headers/cache-control/index.md | HTTP - Headers - Cache-Control - Use Cases - Clearing an already-stored cache:
There are no cache directives for clearing already-stored responses from caches on intermediate servers.
Imagine that clients/caches store a fresh response for a path, with no request flight to the server. There is nothing a server could d... | [
0.13183073699474335,
-0.30855870246887207,
-1.0005555152893066,
0.04417950659990311,
-0.3448199927806854,
-2.3073034286499023,
0.5257245302200317,
1.266632080078125,
-0.628190815448761,
-0.40879565477371216,
0.0361434742808342,
0.12240423262119293,
-0.49298444390296936,
0.45713651180267334... |
http/reference/headers/critical-ch/index.md | HTTP - Headers - Critical-CH:
Secure context: This feature is available only in secure contexts (HTTPS). Non-standard: This feature is not standardized.
The HTTP `Critical-CH` `response header` is used along with `Accept-CH` to identify the accepted client hints that are critical.
User agents receiving a response wi... | [
-0.7894707322120667,
-0.2937963902950287,
-0.9422784447669983,
0.5251125693321228,
-0.23882311582565308,
-1.4537354707717896,
0.8348370790481567,
0.09085632115602493,
-0.46564191579818726,
0.10794777423143387,
-0.5913391709327698,
-0.1874309778213501,
0.21942107379436493,
-0.03737889230251... |
http/reference/headers/critical-ch/index.md | HTTP - Headers - Critical-CH - Syntax:
Example:
Critical-CH: <ch-list> | [
0.21996961534023285,
-0.12271112948656082,
-0.5269923210144043,
0.004323884844779968,
-0.4412829577922821,
-1.0142896175384521,
0.9281576871871948,
1.3136868476867676,
-0.42007124423980713,
0.005670187994837761,
-0.5537490844726562,
-0.16863815486431122,
0.010120484977960587,
-0.4274445176... |
http/reference/headers/critical-ch/index.md | HTTP - Headers - Critical-CH - Syntax - Directives:
- `<ch-list>`: A list of one or more comma-delimited client hint headers that the server considers to be critical client hints. | [
-1.1492700576782227,
-0.9112975001335144,
-0.9575695395469666,
0.14305497705936432,
-0.4567195475101471,
-1.374172329902649,
0.503023624420166,
0.6502587199211121,
-0.4942183494567871,
-0.14119715988636017,
-0.12875594198703766,
-0.5362770557403564,
-0.1958765983581543,
0.02658820897340774... |
http/reference/headers/critical-ch/index.md | HTTP - Headers - Critical-CH - Examples:
The client makes an initial request to the server:
Example:
GET / HTTP/1.1
Host: example.com
The server responds, indicating via `Accept-CH` that it accepts `Sec-CH-Prefers-Reduced-Motion`. In this example, `Critical-CH` is also used to specify that `Sec-CH-Prefers-Reduced-M... | [
-0.611322283744812,
-0.10463833063840866,
-0.9610097408294678,
0.9250842332839966,
-0.3229984641075134,
-1.4418480396270752,
0.7099814414978027,
0.0678342953324318,
-0.9108719229698181,
0.3659861981868744,
-0.3851669132709503,
-0.33577820658683777,
-0.29869306087493896,
-0.1383934020996093... |
http/reference/headers/repr-digest/index.md | HTTP - Headers - Repr-Digest:
The HTTP `Repr-Digest` `request` and `response header` provides a `digest` of the selected representation of the target resource. It can be used validate the integrity of the whole selected representation once it has been received and reconstructed.
The selected representation is the spe... | [
-0.4868558645248413,
-0.8087474703788757,
-0.5426269769668579,
0.6339563131332397,
-0.5130622386932373,
-1.7780661582946777,
1.168887972831726,
0.26466014981269836,
0.02808808535337448,
0.42327603697776794,
-0.18058425188064575,
0.5488455891609192,
-0.5213602781295776,
0.49163317680358887,... |
http/reference/headers/repr-digest/index.md | HTTP - Headers - Repr-Digest - Syntax:
Example:
Repr-Digest: <digest-algorithm>=<digest-value>
// Multiple digest algorithms
Repr-Digest: <digest-algorithm>=<digest-value>,…,<digest-algorithmN>=<digest-valueN> | [
0.21090732514858246,
-0.3867318332195282,
0.06954354047775269,
0.08747027814388275,
-1.6376378536224365,
-0.8371347784996033,
0.4634970426559448,
1.5939923524856567,
0.5125205516815186,
0.15784752368927002,
-0.5934944748878479,
0.22812756896018982,
-0.7211669683456421,
0.4404349625110626,
... |
http/reference/headers/repr-digest/index.md | HTTP - Headers - Repr-Digest - Directives:
- `<digest-algorithm>`: The algorithm used to create a digest of the representation. Only two registered digest algorithms are considered secure: `sha-512` and `sha-256`. The insecure (legacy) registered digest algorithms are: `md5`, `sha` (SHA-1), `unixsum`, `unixcksum`, `ad... | [
-0.20017549395561218,
-0.7389088869094849,
-1.1268080472946167,
0.3617187440395355,
-0.6753462553024292,
-0.2257698029279709,
0.9267427921295166,
0.6214480996131897,
0.4804939031600952,
0.5091185569763184,
-1.753745675086975,
0.21021351218223572,
-0.30266958475112915,
-0.30193227529525757,... |
http/reference/headers/repr-digest/index.md | HTTP - Headers - Repr-Digest - Description:
A `Digest` header was defined in previous specifications, but it proved problematic as the scope of what the digest applied to was not clear. Specifically, it was difficult to distinguish whether a digest applied to the entire resource representation or to the specific conte... | [
-0.4241574704647064,
-1.3839651346206665,
-0.7496955990791321,
0.3257790803909302,
-0.8593458533287048,
-1.7054673433303833,
0.188873752951622,
0.9774227142333984,
0.1367083340883255,
0.12538805603981018,
0.15503670275211334,
0.012331657111644745,
-0.690179705619812,
0.08731351792812347,
... |
http/reference/headers/repr-digest/index.md | HTTP - Headers - Repr-Digest - Examples - User-agent sending a Repr-Digest in requests:
In the following example, a user-agent sends a digest of the message content using SHA-512. It sends both a `Content-Digest` and a `Repr-Digest`, which differ from each other because of the `Content-Encoding`:
Example:
POST /bank... | [
-0.6528995633125305,
-0.7530073523521423,
-0.489497572183609,
-0.07524753361940384,
-0.251279354095459,
-0.966523289680481,
1.1937066316604614,
-0.011286317370831966,
-0.24124252796173096,
0.19468720257282257,
-0.3455257713794708,
0.1526380181312561,
-0.9507681727409363,
0.2282919585704803... |
http/reference/headers/repr-digest/index.md | HTTP - Headers - Repr-Digest - Examples - HTTP response where `Repr-Digest` and `Content-Digest` coincide:
An HTTP server may send the whole representation unencoded in a single message. In this case, `Repr-Digest` and `Content-Digest` have equal values for the same digest algorithms:
Example:
…
Repr-Digest: sha-256... | [
-1.5660837888717651,
-0.6664161682128906,
0.08538763970136642,
-0.23448486626148224,
-0.509909987449646,
-1.623083472251892,
-0.19697710871696472,
0.6834380626678467,
-0.26146212220191956,
0.4788258969783783,
-0.4139467775821686,
0.3513091206550598,
-0.2768879532814026,
0.3394283056259155,... |
http/reference/headers/repr-digest/index.md | HTTP - Headers - Repr-Digest - Examples - HTTP responses where `Repr-Digest` and `Content-Digest` diverge:
A server may compress the content for sending. In this case `Content-Digest` will depend on the `Content-Encoding`, and will therefore have a different value to the `Repr-Digest` header in a response:
Example:
... | [
-0.3081136643886566,
-0.846501350402832,
0.6226389408111572,
0.28881117701530457,
0.2763861119747162,
-1.8833324909210205,
0.2276676893234253,
1.4094289541244507,
0.24991312623023987,
0.006999521516263485,
-0.7864972949028015,
0.4349583387374878,
-0.7448589205741882,
0.15704026818275452,
... |
http/reference/headers/repr-digest/index.md | HTTP - Headers - Repr-Digest - Examples - Successful HTTP request-response employing `Want-Repr-Digest`, `Repr-Digest`, and `Content-Digest`:
The following `PUT` request includes a `Want-Repr-Digest` header, indicating that the server should include a `Repr-Digest` header with a `sha-256` digest if the operation is su... | [
-0.17527104914188385,
-0.4939831793308258,
-0.30921947956085205,
0.9848932027816772,
0.2892910838127136,
-2.064072608947754,
-0.40123429894447327,
0.6877515316009521,
-0.10980251431465149,
-0.3489128649234772,
-0.7734051942825317,
0.34017452597618103,
-0.5445945858955383,
0.050584122538566... |
http/reference/headers/repr-digest/index.md | HTTP - Headers - Repr-Digest - Examples - Unsuccessful HTTP request-response employing `Repr-Digest`:
In the following message, a user-agent requests a resource with a specific sha-256 digest:
Example:
GET /api/last-transaction HTTP/1.1
Accept: text/json
Repr-Digest: sha-256=:2IBI7hQn83oTCgB3Z/6apOl91WGoctRfRj/F9gkv... | [
-1.4250860214233398,
-0.0854647159576416,
-0.4881938099861145,
-0.15488028526306152,
-0.8552873134613037,
-0.38998183608055115,
1.0060545206069946,
0.4697760343551636,
-0.07422240823507309,
0.3923967182636261,
-0.725210428237915,
0.13473087549209595,
-0.675212562084198,
-0.3271283507347107... |
http/reference/headers/sec-gpc/index.md | HTTP - Headers - Sec-GPC:
The HTTP `Sec-GPC` `request header` is part of the Global Privacy Control (GPC) mechanism to indicate whether the user consents to a website or service selling or sharing their personal information with third parties.
The specification does not define how the user can withdraw or grant conse... | [
-1.690572738647461,
-0.6443095207214355,
-1.6145265102386475,
0.3578745424747467,
-0.17224088311195374,
-1.560906171798706,
0.5828968286514282,
0.06775546073913574,
0.1159401535987854,
0.48208752274513245,
-0.9014220833778381,
0.5881659388542175,
-0.14265099167823792,
-0.035937242209911346... |
http/reference/headers/sec-gpc/index.md | HTTP - Headers - Sec-GPC - Syntax:
Example:
Sec-GPC: <preference> | [
-0.4482713043689728,
0.018712814897298813,
-0.936291515827179,
0.13054049015045166,
-0.7047713398933411,
-1.5152897834777832,
1.265820026397705,
1.7092716693878174,
0.8481499552726746,
0.09248598664999008,
-0.2541794180870056,
0.2687402367591858,
0.32000115513801575,
-0.1596660017967224,
... |
http/reference/headers/sec-gpc/index.md | HTTP - Headers - Sec-GPC - Directives:
- `<preference>`: A value of `1` means the user has indicated that they prefer their information not be shared with, or sold to, third parties. Otherwise, the header is not sent, which indicates that either the user has not made a decision or the user is okay with their informati... | [
-0.8943853378295898,
-0.68896484375,
-1.65328049659729,
0.5493201613426208,
-0.3597371578216553,
-1.226130485534668,
1.0168837308883667,
0.47366970777511597,
0.37292060256004333,
-0.0745171308517456,
-0.3594782054424286,
0.12491415441036224,
-0.46813854575157166,
-0.6584571003913879,
0.0... |
http/reference/headers/sec-gpc/index.md | HTTP - Headers - Sec-GPC - Examples - Reading Global Privacy Control status from JavaScript:
The user's GPC preference can also be read from JavaScript using the `Navigator.globalPrivacyControl` or `WorkerNavigator.globalPrivacyControl` property:
Example:
navigator.globalPrivacyControl; // "false" or "true" | [
-1.6401759386062622,
-0.3159032464027405,
-0.648848831653595,
0.27575773000717163,
-0.3539603054523468,
-1.7285819053649902,
0.9257766008377075,
-0.2162088006734848,
0.09607891738414764,
0.723741888999939,
-1.1676167249679565,
-0.9528825879096985,
-0.45621997117996216,
-0.6247568726539612,... |
http/reference/headers/idempotency-key/index.md | HTTP - Headers - Idempotency-Key:
Non-standard: This feature is not standardized.
The HTTP `Idempotency-Key` `request header` can be used to make `POST` and `PATCH` requests `idempotent`.
This allows clients to resend unacknowledged requests without having to be concerned that the request has already been received a... | [
-0.44339579343795776,
0.2418805956840515,
-0.6567486524581909,
0.1501387357711792,
-0.6060552597045898,
-1.8861563205718994,
1.1480114459991455,
0.8109685182571411,
-0.526156485080719,
-0.25596511363983154,
-1.26994788646698,
1.0304911136627197,
-0.12418138980865479,
0.17214694619178772,
... |
http/reference/headers/idempotency-key/index.md | HTTP - Headers - Idempotency-Key - Syntax:
Example:
Idempotency-Key: <key> | [
0.7894328832626343,
0.23935070633888245,
-0.7550299167633057,
-0.9393386840820312,
-1.1733653545379639,
-1.5121757984161377,
1.6573196649551392,
2.3233447074890137,
0.18457144498825073,
-0.5881145596504211,
-0.8536543250083923,
0.11038050055503845,
-0.413045197725296,
-0.15663188695907593,... |
http/reference/headers/idempotency-key/index.md | HTTP - Headers - Idempotency-Key - Directives:
- `<key>`: The unique key for a particular request. The format is defined by the server. | [
0.09358970075845718,
0.2002277374267578,
-1.175848126411438,
-0.5518591403961182,
-1.0667461156845093,
-1.4382706880569458,
1.0169764757156372,
0.8104453682899475,
0.19764012098312378,
-0.15087875723838806,
-0.3071102499961853,
0.07998859882354736,
-0.1497076451778412,
0.41958993673324585,... |
http/reference/headers/idempotency-key/index.md | HTTP - Headers - Idempotency-Key - Description:
The HTTP methods `GET`, `HEAD`, `PUT`, `DELETE`, and `OPTIONS` are idempotent. What this means is that you can send a message with these methods any number of times and the state of the server either won't be changed, or will be changed in the same way every time it gets... | [
-0.9374134540557861,
0.022499263286590576,
-0.2883009910583496,
-0.24944943189620972,
-0.466601699590683,
-2.354017734527588,
1.2386568784713745,
0.6290337443351746,
-0.49034667015075684,
-0.2771646976470947,
-0.2821715474128723,
0.5294786095619202,
-0.4031766951084137,
-0.1294388771057129... |
http/reference/headers/idempotency-key/index.md | HTTP - Headers - Idempotency-Key - Description - Client responsibilities:
Client JavaScript should attach the `Idempotency-Key` header in fetch requests for endpoints that require it, with a key that conforms to the requirements published by the server.
A unique key must be used for each new request that is sent, and... | [
-0.6713017821311951,
-0.1361459493637085,
-1.0028334856033325,
-0.2561175227165222,
-0.5934587121009827,
-0.9853924512863159,
1.680548906326294,
-0.018310673534870148,
-0.9739056825637817,
-0.4006251394748688,
-0.46626952290534973,
0.34001103043556213,
-0.7864164710044861,
0.11495979130268... |
http/reference/headers/idempotency-key/index.md | HTTP - Headers - Idempotency-Key - Description - Server responsibilities:
Servers that support the `Idempotency-Key` header are expected to document and publish their support, including the endpoints that require the header, and any requirements on the key (such as length, computation method, and expiry).
Note that t... | [
-0.7739397287368774,
-0.4579084813594818,
-1.0096302032470703,
0.0660267025232315,
-0.8132759928703308,
-1.4528154134750366,
1.0941481590270996,
0.6057915687561035,
-0.07224667817354202,
-0.22569851577281952,
0.10120335221290588,
-0.19202649593353271,
-0.501737117767334,
0.8974874019622803... |
http/reference/headers/idempotency-key/index.md | HTTP - Headers - Idempotency-Key - Description - Server responsibilities - Idempotency fingerprint:
A unique key is expected to be used in each request.
In order to protect against clients reusing keys for new requests, a server may create and store an "idempotency fingerprint" of the request along with the key. This... | [
-0.34793591499328613,
-0.14983630180358887,
-1.0141197443008423,
0.043122678995132446,
-0.32948803901672363,
-1.4090385437011719,
0.9477847814559937,
0.8161783814430237,
-0.5290931463241577,
-0.22835597395896912,
-0.281372606754303,
0.928139328956604,
-0.3696296811103821,
0.251514971256256... |
http/reference/headers/idempotency-key/index.md | HTTP - Headers - Idempotency-Key - Description - Server responsibilities - Request processing:
On receiving a `POST` or `PATCH` request with an `Idempotency-Key` on an endpoint that requires it, the server should check whether it already has received a request with that key.
- If it hasn't, the server should perform ... | [
-0.5097355246543884,
-0.28690072894096375,
-0.545637845993042,
0.10117141902446747,
-0.6347940564155579,
-1.231714129447937,
1.0588085651397705,
0.5933266282081604,
-0.6731358170509338,
-0.03848133981227875,
0.5759301781654358,
0.31459489464759827,
-0.35216888785362244,
0.8753939867019653,... |
http/reference/headers/idempotency-key/index.md | HTTP - Headers - Idempotency-Key - Description - Server responsibilities - Server error responses:
A server should provide error responses in the following cases:
- `400`: The header is omitted for an endpoint that is documented as requiring it.
- `409`: A request with the same key is currently/still being processed.... | [
-1.0754481554031372,
-0.18037989735603333,
-0.8673881888389587,
-0.17586970329284668,
-0.021603047847747803,
-1.0620620250701904,
1.018196940422058,
0.9123387336730957,
-0.808457612991333,
0.14789508283138275,
-0.08244043588638306,
0.40904730558395386,
-0.350564569234848,
0.665632247924804... |
http/reference/headers/idempotency-key/index.md | HTTP - Headers - Idempotency-Key - Examples - A `POST` request with a key:
The following message shows a `POST` request to create a new user. The key `9c7d2b4a0e1f6c835a2d1b0f4e3c5a7d` is a unique value that matches the requirements published by the host (example.com doesn't support this header, so we've just made up ... | [
0.054369185119867325,
0.04676244035363197,
-0.17652912437915802,
0.12189328670501709,
0.12488256394863129,
-1.4848159551620483,
0.6401553750038147,
0.18975724279880524,
-0.8389558792114258,
-0.4430420696735382,
-0.006028374657034874,
0.9084503054618835,
-0.2031886726617813,
0.0223145410418... |
http/reference/headers/server-timing/index.md | HTTP - Headers - Server-Timing:
The HTTP `Server-Timing` `response header` communicates one or more performance metrics about the request-response cycle to the user agent. It is used to surface backend server timing metrics (for example, database read/write, CPU time, file system access, etc.) in the developer tools i... | [
-0.88072669506073,
-0.4542136490345001,
-1.770563006401062,
0.5998750329017639,
-0.38431569933891296,
-1.7821521759033203,
-0.06537629663944244,
0.5077192187309265,
-0.20709195733070374,
-0.07746998965740204,
-0.6448479294776917,
0.2490920126438141,
-0.2141285538673401,
0.02182786911725998... |
http/reference/headers/server-timing/index.md | HTTP - Headers - Server-Timing - Syntax:
Example:
// A single metric
Server-Timing: <timing-metric>
// Multiple metrics as a comma-separated list
Server-Timing: <timing-metric>, …, <timing-metricN>
A `<timing-metric>` has a name, and may include an optional duration and an optional description. For example:
Exampl... | [
-0.8562236428260803,
-0.3515460193157196,
-1.0995742082595825,
0.09728257358074188,
-0.40369972586631775,
-1.632070541381836,
-0.2159668654203415,
1.066841959953308,
-0.6558148860931396,
0.17414937913417816,
0.32161253690719604,
-0.1745578497648239,
0.41498348116874695,
-0.2335236370563507... |
http/reference/headers/server-timing/index.md | HTTP - Headers - Server-Timing - Directives:
- `<timing-metric>`: A comma-separated list of one or more metrics with the following components separated by semi-colons:
- `<name>`: A name token (no spaces or special characters) for the metric that is implementation-specific or defined by the server, like `cacheHit`.
... | [
-0.6824200749397278,
-1.053057074546814,
-1.072168231010437,
0.3119741976261139,
-0.6448391079902649,
-1.8226628303527832,
0.24607884883880615,
0.39841100573539734,
-0.48108431696891785,
0.6349751353263855,
0.051182739436626434,
0.10992437601089478,
0.35023149847984314,
0.13035038113594055... |
http/reference/headers/server-timing/index.md | HTTP - Headers - Server-Timing - Description - Privacy and security:
The `Server-Timing` header may expose potentially sensitive application and infrastructure information. Decide which metrics to send, when to send them, and who should see them based on the use case. For example, you may decide to only show metrics t... | [
-0.5339928269386292,
-0.055069662630558014,
-0.9925636649131775,
0.8424848914146423,
-0.5762976408004761,
-1.6030330657958984,
0.22848418354988098,
0.449290931224823,
-0.013879768550395966,
-0.34895485639572144,
-0.615730881690979,
0.36696726083755493,
0.4361172318458557,
-1.27904701232910... |
http/reference/headers/server-timing/index.md | HTTP - Headers - Server-Timing - Description - PerformanceServerTiming interface:
In addition to having `Server-Timing` header metrics appear in the developer tools of the browser, the `PerformanceServerTiming` interface enables tools to automatically collect and process metrics from JavaScript. This interface is rest... | [
0.1514960676431656,
-0.6261781454086304,
-0.9859282970428467,
0.8233336210250854,
0.12502320110797882,
-1.3082150220870972,
0.43887144327163696,
0.6511207222938538,
0.4982406497001648,
0.3427935838699341,
-0.5853073000907898,
0.5972740650177002,
0.7739056944847107,
-0.10397381335496902,
... |
http/reference/headers/server-timing/index.md | HTTP - Headers - Server-Timing - Examples - Sending a metric using the Server-Timing header:
The following response includes a metric `custom-metric` with a duration of `123.45` milliseconds, and a description of "My custom metric":
Example:
Server-Timing: custom-metric;dur=123.45;desc="My custom metric" | [
-1.0120097398757935,
-0.27040594816207886,
-0.9008204340934753,
0.16601428389549255,
-0.7362406849861145,
-1.382258415222168,
-0.27297142148017883,
0.12041972577571869,
-0.4474959075450897,
-0.03933313116431236,
-0.0593801848590374,
0.7061101198196411,
0.7875058650970459,
-0.20807637274265... |
http/reference/headers/server-timing/index.md | HTTP - Headers - Server-Timing - Examples - Server-Timing as HTTP trailer:
In the following response, the `Trailer` header is used to indicate that a `Server-Timing` header will follow the response body. A metric `custom-metric` with a duration of `123.4` milliseconds is sent.
Example:
HTTP/1.1 200 OK
Transfer-Encod... | [
-1.2110086679458618,
-0.40950092673301697,
-0.80618816614151,
0.6845219731330872,
-0.7451102137565613,
-1.1850700378417969,
-0.19953595101833344,
0.3762052059173584,
-0.7966871857643127,
0.17836786806583405,
-0.09743871539831161,
0.17538484930992126,
0.8790128827095032,
0.1281765252351761,... |
http/reference/headers/content-security-policy/connect-src/index.md | HTTP - Headers - Content-Security-Policy - connect-src:
The HTTP `Content-Security-Policy` (CSP) `connect-src` directive restricts the URLs which can be loaded using script interfaces. The following APIs are controlled by this directive:
- The `ping` attribute in `a` elements
- `fetch()`
- `fetchLater()` (experimenta... | [
-0.7499428987503052,
-1.0643165111541748,
-0.7082071304321289,
0.10212334990501404,
-0.03479865565896034,
-1.253049373626709,
0.35087090730667114,
1.183262825012207,
-0.03745273873209953,
0.06575095653533936,
-0.5084632635116577,
0.684901237487793,
-0.031162749975919724,
-0.430687576532363... |
http/reference/headers/content-security-policy/connect-src/index.md | HTTP - Headers - Content-Security-Policy - connect-src - Syntax:
Example:
Content-Security-Policy: connect-src 'none';
Content-Security-Policy: connect-src <source-expression-list>;
This directive may have one of the following values:
- `'none'`: No resources of this type may be loaded. The single quotes are mandat... | [
-0.8701017498970032,
0.12978501617908478,
-0.7635970115661621,
0.4005787670612335,
-0.7113837003707886,
-1.64833402633667,
0.7156129479408264,
1.570475459098816,
0.432223379611969,
0.0016889190301299095,
0.5968223810195923,
0.05532025545835495,
-0.3305940330028534,
-1.0931142568588257,
0... |
http/reference/headers/content-security-policy/connect-src/index.md | HTTP - Headers - Content-Security-Policy - connect-src - Examples - Violation cases:
Given this CSP header:
Example:
Content-Security-Policy: connect-src https://example.com/
The following connections are blocked and won't load:
Example:
<a ping="https://not-example.com" href="/">Link</a>
<script>
const respons... | [
-0.11186404526233673,
-0.8727034330368042,
-0.5968219041824341,
0.3563239276409149,
-0.4241359829902649,
-0.8974674940109253,
-0.19045472145080566,
1.2816797494888306,
-0.29554283618927,
-0.0758223682641983,
-0.12044290453195572,
0.9948958158493042,
0.1394989937543869,
-0.8327423334121704,... |
http/reference/headers/x-frame-options/index.md | HTTP - Headers - X-Frame-Options:
Note: For more comprehensive options than offered by this header, see the `frame-ancestors` directive in a `Content-Security-Policy` header.
The HTTP `X-Frame-Options` `response header` can be used to indicate whether a browser should be allowed to render the document in a `frame`, `... | [
-0.7974854111671448,
-0.9121020436286926,
-0.6528165936470032,
1.263106107711792,
-1.0282143354415894,
-1.6108814477920532,
1.1703686714172363,
0.8834362626075745,
0.3954414129257202,
-0.16245974600315094,
-0.38345640897750854,
-0.36583924293518066,
0.4590325653553009,
-0.43430009484291077... |
http/reference/headers/x-frame-options/index.md | HTTP - Headers - X-Frame-Options - Syntax:
Example:
X-Frame-Options: DENY
X-Frame-Options: SAMEORIGIN | [
0.6064823269844055,
-0.6786274909973145,
-0.3581657409667969,
-0.08343677967786789,
-1.6694022417068481,
-0.8867721557617188,
1.4602175951004028,
1.779303789138794,
0.49610376358032227,
-0.28336408734321594,
-0.26349717378616333,
-0.848372220993042,
0.3100956082344055,
-0.3209424614906311,... |
http/reference/headers/x-frame-options/index.md | HTTP - Headers - X-Frame-Options - Syntax - Directives:
- `DENY`: The document cannot be loaded in any frame, regardless of origin (both same- and cross-origin embedding is blocked).
- `SAMEORIGIN`: The document can only be embedded if all ancestor frames have the same `origin` as the page itself.
- `ALLOW-FROM origin... | [
0.7066671848297119,
-0.593989372253418,
-0.5572976469993591,
-0.07147907465696335,
-1.2196871042251587,
-1.8917617797851562,
1.2336636781692505,
0.8800064325332642,
0.32240137457847595,
-0.3339345455169678,
-0.5794814229011536,
-0.8651259541511536,
-0.2871445119380951,
0.3982204496860504,
... |
http/reference/headers/x-frame-options/index.md | HTTP - Headers - X-Frame-Options - Examples:
Warning: Setting `X-Frame-Options` inside the `meta` element (e.g., `<meta http-equiv="X-Frame-Options" content="deny">`) has no effect. `X-Frame-Options` is only enforced via HTTP headers, as shown in the examples below. | [
-0.2942521870136261,
-0.8698158264160156,
-0.7390714287757874,
0.4180485010147095,
-1.355838418006897,
-1.2525616884231567,
1.4641356468200684,
1.8834596872329712,
-0.1925998330116272,
-0.17440271377563477,
-0.37796223163604736,
-0.8750608563423157,
0.2809195816516876,
-0.9279423356056213,... |
http/reference/headers/x-frame-options/index.md | HTTP - Headers - X-Frame-Options - Examples - Configuring Apache:
To configure Apache to send the `X-Frame-Options` header for all pages, add this to your site's configuration:
Example:
Header always set X-Frame-Options "SAMEORIGIN"
To configure Apache to set `X-Frame-Options` to `DENY`, add this to your site's con... | [
0.0709332674741745,
-1.0712798833847046,
-0.8449268937110901,
0.7964562773704529,
-1.3576546907424927,
-1.1473188400268555,
2.551814556121826,
1.2317430973052979,
-0.18241995573043823,
-0.3043501377105713,
0.10906234383583069,
-0.4663732051849365,
-0.3708791434764862,
0.3416265845298767,
... |
http/reference/headers/x-frame-options/index.md | HTTP - Headers - X-Frame-Options - Examples - Configuring Nginx:
To configure Nginx to send the `X-Frame-Options` header, add this either to your http, server or location configuration:
Example:
add_header X-Frame-Options SAMEORIGIN always;
You can set the `X-Frame-Options` header to `DENY` using:
Example:
add_he... | [
-1.0562105178833008,
-0.9221957325935364,
0.3590300381183624,
1.1069533824920654,
-1.187222957611084,
-1.2873038053512573,
1.2139471769332886,
0.6444116830825806,
-0.22473245859146118,
-0.23707592487335205,
0.2216413915157318,
-1.0052002668380737,
-0.5622353553771973,
0.41842907667160034,
... |
http/reference/headers/x-frame-options/index.md | HTTP - Headers - X-Frame-Options - Examples - Configuring IIS:
To configure IIS to send the `X-Frame-Options` header, add this to your site's `Web.config` file:
Example:
<system.webServer>
…
<httpProtocol>
<customHeaders>
<add name="X-Frame-Options" value="SAMEORIGIN" />
</customHeaders>
</httpPr... | [
-1.516839861869812,
-0.4887069761753082,
-0.5646228194236755,
0.933201253414154,
-0.9601102471351624,
-0.779620885848999,
1.5236482620239258,
0.6074851751327515,
0.1214916855096817,
0.22674673795700073,
-0.413530558347702,
-0.47812768816947937,
0.15337631106376648,
-0.07289326190948486,
... |
http/reference/headers/x-frame-options/index.md | HTTP - Headers - X-Frame-Options - Examples - Configuring HAProxy:
To configure HAProxy to send the `X-Frame-Options` header, add this to your front-end, listen, or backend configuration:
Example:
rspadd X-Frame-Options:\ SAMEORIGIN
Alternatively, in newer versions:
Example:
http-response set-header X-Frame-Optio... | [
-0.7166998386383057,
-0.7691517472267151,
-0.3002293109893799,
0.41707947850227356,
-0.9660637974739075,
-0.19339606165885925,
1.5773829221725464,
0.7511503100395203,
0.20389461517333984,
0.2425834834575653,
-0.6222997307777405,
-0.5795935392379761,
0.03986898809671402,
0.35149165987968445... |
http/reference/headers/x-frame-options/index.md | HTTP - Headers - X-Frame-Options - Examples - Configuring Express:
To set `X-Frame-Options` to `SAMEORIGIN` using Helmet add the following to your server configuration:
Example:
import helmet from "helmet";
const app = express();
app.use(
helmet({
xFrameOptions: { action: "sameorigin" },
}),
); | [
0.164824441075325,
-1.0341038703918457,
-0.9120115041732788,
0.46494632959365845,
-1.1681318283081055,
-1.2994037866592407,
0.9747999906539917,
1.1442381143569946,
0.6627570986747742,
-0.07496479153633118,
-0.3671051263809204,
-0.598358154296875,
0.37123164534568787,
-0.4577043354511261,
... |
http/reference/status/402/index.md | HTTP - Status - 402:
The HTTP `402 Payment Required` client error response status code is a nonstandard response status code reserved for future use.
This status code was created to enable digital cash or (micro) payment systems and would indicate that requested content is not available until the client makes a payme... | [
-0.9987323880195618,
-0.1520550400018692,
-0.8599496483802795,
-0.07384801656007767,
0.03527642786502838,
-0.7679305672645569,
0.651247501373291,
0.9481062293052673,
-0.7263890504837036,
0.47344711422920227,
0.037126995623111725,
0.3795763850212097,
-0.08085738122463226,
-0.113424509763717... |
http/reference/status/402/index.md | HTTP - Status - 402 - Status:
Example:
402 Payment Required | [
-0.40317291021347046,
0.20528165996074677,
-0.9964078664779663,
-0.008906513452529907,
-0.8049870729446411,
0.9655258059501648,
1.3691112995147705,
1.4644054174423218,
-0.8105464577674866,
-0.32236960530281067,
0.1686343550682068,
0.21915459632873535,
0.17540548741817474,
-0.03465721756219... |
http/reference/status/402/index.md | HTTP - Status - 402 - Examples - Payment API failure:
Some payment APIs use the 402 response as a generic catch-all for failed payment requests. The following example tries to make a call to a payment API using a POST request to initiate a transaction:
Example:
POST /merchant/transfers/payment HTTP/1.1
Host: payment... | [
0.33830562233924866,
-0.3814700245857239,
-0.9589811563491821,
0.3691078722476959,
0.461525559425354,
-1.1404451131820679,
-0.21187223494052887,
1.2426106929779053,
-0.30628979206085205,
0.12537208199501038,
0.3899608254432678,
0.8915377259254456,
0.1979404240846634,
-0.06837983429431915,
... |
http/reference/status/402/index.md | HTTP - Status - 402 - Compatibility notes:
This status code is reserved but not defined. Actual implementations vary in the format and contents of the response. No browser supports a 402, and an error will be displayed as a generic `4xx` status code. | [
-0.40766361355781555,
0.08930232375860214,
-0.8000301718711853,
-0.26249486207962036,
-0.6019721627235413,
-0.4015152156352997,
0.9247806668281555,
1.1648330688476562,
0.5270743370056152,
0.20792841911315918,
-0.43571117520332336,
0.373654305934906,
0.252289354801178,
-0.012911289930343628... |
svg/reference/element/script/index.md | SVG - Element - script:
The `<script>` SVG element allows to add scripts to an SVG document.
Note: While SVG's `script` element is equivalent to the HTML `script` element, it has some discrepancies, like it uses the `href` attribute instead of `src` and it doesn't support ECMAScript modules so far (See browser compat... | [
-1.3884538412094116,
-0.4196225702762604,
-0.21626852452754974,
0.3429719805717468,
0.2563197910785675,
-1.6734596490859985,
0.9082269668579102,
1.0899314880371094,
0.3085061311721802,
-0.8608000874519348,
0.36652156710624695,
0.14219103753566742,
-0.245555117726326,
-0.1442563533782959,
... |
svg/reference/element/script/index.md | SVG - Element - script - Attributes:
- `async` (experimental): If the `async` attribute is present, then the external script will be fetched in parallel to parsing and evaluated as soon as it is available. Equivalent to the `async` attribute on the HTML `script` element. Value type: boolean; Default value: none; Anima... | [
-0.8809630274772644,
-0.6896637678146362,
-0.45520836114883423,
0.38909289240837097,
-0.1753096729516983,
-0.9820103645324707,
0.19600439071655273,
0.8988014459609985,
-0.36551982164382935,
-0.19642233848571777,
0.02637971192598343,
0.846421480178833,
0.3211360275745392,
0.0204574614763259... |
svg/reference/element/script/index.md | SVG - Element - script - DOM Interface:
This element implements the `SVGScriptElement` interface. | [
-0.47600263357162476,
-0.34374523162841797,
-0.058807894587516785,
-0.38985589146614075,
-0.46047961711883545,
-1.1918435096740723,
1.4085445404052734,
0.8920460343360901,
0.31696173548698425,
-0.3582371771335602,
0.4760035276412964,
-0.26351210474967957,
0.34585461020469666,
-0.2931324839... |
svg/reference/element/script/index.md | SVG - Element - script - Example:
Example:
Click the circle to change colors.
<svg
viewBox="0 0 10 10"
height="120px"
width="120px"
xmlns="http://www.w3.org/2000/svg">
<circle cx="5" cy="5" r="4" />
<script>
// <![CDATA[
function getColor() {
const R = Math.round(Math.random() * 255)
... | [
-1.8126124143600464,
0.14620622992515564,
-0.13531848788261414,
-0.47088930010795593,
-0.43701374530792236,
-1.1083812713623047,
0.6974330544471741,
0.7361829876899719,
-0.9020479917526245,
-0.14019827544689178,
0.4510710835456848,
0.10636360943317413,
-0.16911853849887848,
-0.362301081418... |
svg/reference/element/use/index.md | SVG - Element - use:
The `<use>` element takes nodes from within an SVG document, and duplicates them somewhere else. The effect is the same as if the nodes were deeply cloned into a non-exposed DOM, then pasted where the `<use>` element is, much like cloned `template` elements. | [
-0.47460031509399414,
-0.65001380443573,
-1.1945050954818726,
0.457968533039093,
-0.03957599774003029,
-1.5171363353729248,
1.6683070659637451,
1.5009552240371704,
-0.4125420153141022,
0.06519103795289993,
-0.046221405267715454,
0.5749816298484802,
-0.7493668794631958,
0.02613648772239685,... |
svg/reference/element/use/index.md | SVG - Element - use - Attributes:
- `href`: The URL to an element/fragment that needs to be duplicated. See Usage notes for details on common pitfalls. Value type: `<URL>`; Default value: none; Animatable: yes
- `xlink:href` (deprecated): An `<IRI>` reference to an element/fragment that needs to be duplicated. If both... | [
-0.22555267810821533,
-0.4223778545856476,
-0.3213645815849304,
0.4914397597312927,
0.5695787072181702,
-1.5710620880126953,
0.6815047264099121,
1.0727366209030151,
-0.6159932017326355,
0.07360418140888214,
-0.47252991795539856,
0.10635700821876526,
0.1940585821866989,
0.11183375120162964,... |
svg/reference/element/use/index.md | SVG - Element - use - DOM Interface:
This element implements the `SVGUseElement` interface. | [
0.16020645201206207,
-0.14401781558990479,
-0.16444113850593567,
-0.38423192501068115,
-0.8848830461502075,
-1.1193459033966064,
1.6595791578292847,
0.9597404599189758,
0.43050646781921387,
0.15514186024665833,
0.4433715045452118,
0.014465056359767914,
0.9216282367706299,
-0.37234860658645... |
svg/reference/element/use/index.md | SVG - Element - use - Example:
The following example shows how to use the `<use>` element to draw multiple circles with different fill and stroke colors.
Example:
html,
body,
svg {
height: 100%;
}
Example:
<svg viewBox="0 0 30 10" xmlns="http://www.w3.org/2000/svg">
<circle id="myCircle" cx="5" cy="5" r="4" />... | [
-0.9543488621711731,
-0.29177984595298767,
-0.3202778398990631,
0.5364893078804016,
-0.02652788907289505,
-1.0987108945846558,
1.2788294553756714,
0.4372333586215973,
-0.3281811475753784,
-0.117767333984375,
0.37544286251068115,
0.6732844114303589,
0.27865731716156006,
-0.4369611442089081,... |
svg/reference/element/use/index.md | SVG - Element - use - Usage notes:
Most attributes on `<use>` are ignored if the corresponding attribute is already defined on the element referenced by `<use>`. (This differs from how CSS style attributes override those set 'earlier' in the cascade). Only the attributes `x`, `y`, `width`, `height` and `href` on the `... | [
-0.13256733119487762,
-0.1330297291278839,
-0.7942538261413574,
0.05421940237283707,
0.08058929443359375,
-1.2451857328414917,
0.322322279214859,
0.6163216233253479,
-0.05698937177658081,
0.1910623162984848,
0.3781711161136627,
-0.09300434589385986,
0.5221410393714905,
0.43137598037719727,... |
svg/reference/element/use/index.md | SVG - Element - use - Usage notes - Loading resources from external files via `<use>`:
You can load nodes from an external SVG file via the `<use>` element by specifying the path of the file followed by a URL fragment pointing to the `id` of the node to load:
Example:
<svg>
<use href="../assets/my-svg.svg#my-fragm... | [
-0.9389799237251282,
-0.22782309353351593,
-0.5206104516983032,
0.6340941786766052,
-0.42794251441955566,
-0.7215121388435364,
1.9032756090164185,
-0.10285084694623947,
-0.610934317111969,
-0.5008237957954407,
0.352729856967926,
0.2886887490749359,
-0.6581928730010986,
0.26349759101867676,... |
svg/reference/element/use/index.md | SVG - Element - use - Usage notes - Loading resources from data URIs via `<use>`:
Loading resources with data URIs in the `href` attribute is deprecated for security reasons. This applies to `<use href="data:..."` and also when setting `href` by using the `set` or `setAttribute` method.
Again, check the Browser compa... | [
-0.5178646445274353,
-0.4940331280231476,
-0.5141680240631104,
0.9555162787437439,
-0.9939019083976746,
-1.435704231262207,
1.549304485321045,
0.8213695883750916,
-0.12735125422477722,
-1.1341768503189087,
-0.35488417744636536,
-0.1487276405096054,
-0.17177586257457733,
-0.2438465356826782... |
svg/reference/element/fegaussianblur/index.md | SVG - Element - feGaussianBlur:
The `<feGaussianBlur>` SVG filter primitive blurs the input image by the amount specified in `stdDeviation`, which defines the bell-curve.
Like other filter primitives, it handles color components in the `linearRGB` `color space` by default. You can use `color-interpolation-filters` to... | [
-0.48833540081977844,
-1.1064453125,
-0.5349618792533875,
-0.17519718408584595,
0.6380442380905151,
-1.2002427577972412,
0.23601916432380676,
0.9879968166351318,
-0.5624788999557495,
0.7409294247627258,
-0.4582708775997162,
-0.047187987715005875,
0.2184756100177765,
0.06482046842575073,
... |
svg/reference/element/fegaussianblur/index.md | SVG - Element - feGaussianBlur - Attributes:
- `in`
- `stdDeviation`
- `edgeMode`
- Filter primitive attributes: `x`, `y`, `width`, `height`, `result` | [
-1.2780801057815552,
-0.6273584961891174,
-0.6786465644836426,
-0.5232171416282654,
-0.4318186938762665,
-0.5453612804412842,
0.9775669574737549,
0.06130048632621765,
0.0965365320444107,
0.8694829344749451,
-0.4628205895423889,
-0.6248917579650879,
-0.07514555752277374,
0.6265848278999329,... |
svg/reference/element/fegaussianblur/index.md | SVG - Element - feGaussianBlur - DOM Interface:
This element implements the `SVGFEGaussianBlurElement` interface. | [
-0.41437506675720215,
0.1884436309337616,
-0.4906173646450043,
-0.8987575173377991,
-1.0085694789886475,
-0.6012661457061768,
1.357672929763794,
0.5217599272727966,
0.5560839772224426,
0.9039865732192993,
0.4928125739097595,
0.30367594957351685,
0.5591061115264893,
-0.14709283411502838,
... |
svg/reference/element/fegaussianblur/index.md | SVG - Element - feGaussianBlur - Example - Basic example - SVG:
Example:
<svg
width="230"
height="120"
xmlns="http://www.w3.org/2000/svg"
xmlns:xlink="http://www.w3.org/1999/xlink">
<filter id="blurMe">
<feGaussianBlur in="SourceGraphic" stdDeviation="5" />
</filter>
<circle cx="60" cy="60" r="50" ... | [
-1.7435773611068726,
-0.12968087196350098,
-0.9172585010528564,
-0.9805644154548645,
-0.31239378452301025,
-0.8732650876045227,
0.9413306713104248,
0.14817559719085693,
-0.12017733603715897,
0.5421135425567627,
0.6095372438430786,
0.1889135241508484,
-0.2473580539226532,
-0.133059248328208... |
svg/reference/element/fegaussianblur/index.md | SVG - Element - feGaussianBlur - Example - Drop shadow example - SVG:
Example:
<svg
width="120"
height="120"
xmlns="http://www.w3.org/2000/svg"
xmlns:xlink="http://www.w3.org/1999/xlink">
<filter id="dropShadow">
<feGaussianBlur in="SourceAlpha" stdDeviation="3" />
<feOffset dx="2" dy="4" />
<fe... | [
-1.8981804847717285,
-0.3938485383987427,
-1.1590325832366943,
-0.9932534694671631,
-0.05424385517835617,
-0.632122278213501,
1.2360566854476929,
0.4932475686073303,
-0.0959690660238266,
0.5869699120521545,
0.28535833954811096,
-0.08734079450368881,
-0.622843861579895,
0.04479174315929413,... |
svg/reference/attribute/index.md | SVG - Attribute:
SVG elements can be modified using attributes that modify how the element is handled or rendered.
Below is a list of all of the attributes available in SVG, along with links to reference documentation to help you learn which elements support them and how they work. | [
0.01221221499145031,
-0.5672882199287415,
-0.31582194566726685,
0.05526915192604065,
-0.1677059382200241,
-2.379744052886963,
1.2383126020431519,
0.8580682277679443,
0.23102590441703796,
-0.35915040969848633,
0.016547448933124542,
-0.4386714994907379,
-0.1951638013124466,
0.138024330139160... |
svg/reference/attribute/index.md | SVG - Attribute - SVG attributes A to Z - A:
- `accumulate`
- `additive`
- `alignment-baseline`
- `amplitude`
- `attributeName`
- `attributeType`
- `autofocus`
- `azimuth` | [
-0.5888265371322632,
-0.5647855401039124,
-0.3156921863555908,
-0.05448255315423012,
-0.922863245010376,
-1.9839448928833008,
1.5824346542358398,
0.1031719446182251,
0.3110654652118683,
-0.6033835411071777,
-0.06477375328540802,
-0.15081846714019775,
-0.9871202111244202,
0.8091813325881958... |
svg/reference/attribute/index.md | SVG - Attribute - SVG attributes A to Z - B:
- `baseFrequency`
- `baseline-shift`
- `baseProfile`
- `begin`
- `bias`
- `by` | [
-0.33577272295951843,
-0.6201944947242737,
-0.7405164241790771,
0.33473071455955505,
-0.3690102696418762,
-0.5323802828788757,
1.9852073192596436,
0.016920704394578934,
-0.09947780519723892,
-0.5014998912811279,
-0.45998436212539673,
-0.6360533237457275,
-0.39420607686042786,
-0.0061000473... |
svg/reference/attribute/index.md | SVG - Attribute - SVG attributes A to Z - C:
- `calcMode`
- `class`
- `clip`
- `clipPathUnits`
- `clip-path`
- `clip-rule`
- `color`
- `color-interpolation`
- `color-interpolation-filters`
- `crossorigin`
- `cursor`
- `cx`
- `cy` | [
-1.7667522430419922,
-0.3997028172016144,
-0.42910051345825195,
0.24967539310455322,
-0.5491749048233032,
-0.9783974885940552,
-0.022092627361416817,
0.7178147435188293,
-0.6413441300392151,
-0.3504090905189514,
0.39881640672683716,
-0.3970319628715515,
0.9266398549079895,
0.37374389171600... |
svg/reference/attribute/index.md | SVG - Attribute - SVG attributes A to Z - D:
- `d`
- `data-*`
- `decoding`
- `diffuseConstant`
- `direction`
- `display`
- `divisor`
- `dominant-baseline`
- `dur`
- `dx`
- `dy` | [
-0.6968749761581421,
-0.5624103546142578,
-0.6860074996948242,
-0.09743943065404892,
-0.8966807723045349,
-1.104721188545227,
0.46749061346054077,
0.9636325836181641,
0.30964064598083496,
0.13669762015342712,
-0.013977272436022758,
-0.2624044418334961,
-0.5413221716880798,
0.31314605474472... |
svg/reference/attribute/index.md | SVG - Attribute - SVG attributes A to Z - E:
- `edgeMode`
- `elevation`
- `end`
- `exponent` | [
-0.3616243600845337,
-0.7117636799812317,
-0.15721790492534637,
-0.35452377796173096,
-0.7492204308509827,
-0.997481107711792,
1.201181173324585,
1.15715491771698,
0.3658248484134674,
-0.8307388424873352,
0.27768751978874207,
0.10359691083431244,
-0.7372323274612427,
0.48339033126831055,
... |
svg/reference/attribute/index.md | SVG - Attribute - SVG attributes A to Z - F:
- `fetchpriority`
- `fill`
- `fill-opacity`
- `fill-rule`
- `filter`
- `filterUnits`
- `flood-color`
- `flood-opacity`
- `font-family`
- `font-size`
- `font-size-adjust`
- `font-stretch`
- `font-style`
- `font-variant`
- `font-weight`
- `font-width`
- `fr`
- `from`
- `fx`
-... | [
-0.5475424528121948,
0.2355765402317047,
0.36758941411972046,
-0.7526774406433105,
-0.0273633673787117,
-1.0615125894546509,
0.3071984350681305,
1.0244122743606567,
-0.09838651120662689,
-0.45110586285591125,
-0.04960452765226364,
-0.15238456428050995,
-0.1320762038230896,
-0.2618487179279... |
svg/reference/attribute/index.md | SVG - Attribute - SVG attributes A to Z - G:
- `glyph-orientation-horizontal`
- `glyph-orientation-vertical`
- `gradientTransform`
- `gradientUnits` | [
-1.9866523742675781,
-0.33953386545181274,
-0.06350430846214294,
-0.88993901014328,
-0.6011829972267151,
-2.1179962158203125,
0.5780022144317627,
0.3995787501335144,
0.06379970908164978,
-0.8179513216018677,
-0.17042778432369232,
-0.27590036392211914,
-0.03326166421175003,
0.12435302138328... |
svg/reference/attribute/index.md | SVG - Attribute - SVG attributes A to Z - H:
- `height`
- `href`
- `hreflang` | [
-0.7286768555641174,
-0.5084766149520874,
-0.2635060250759125,
0.13715533912181854,
-0.3857128322124481,
-0.755024790763855,
0.8338131308555603,
0.5494239926338196,
-0.6761953830718994,
-1.0183433294296265,
-0.5673215389251709,
-0.024593215435743332,
0.05845862627029419,
0.5550765991210938... |
svg/reference/attribute/index.md | SVG - Attribute - SVG attributes A to Z - I:
- `id`
- `image-rendering`
- `in`
- `in2`
- `intercept` | [
-0.28421738743782043,
-0.21344657242298126,
-0.20265212655067444,
-0.3064996898174286,
-0.5669389367103577,
-1.4146589040756226,
0.64301598072052,
0.6158629059791565,
0.22880807518959045,
-0.656511127948761,
-0.08432410657405853,
-0.7185593247413635,
-0.47764793038368225,
0.186946779489517... |
svg/reference/attribute/index.md | SVG - Attribute - SVG attributes A to Z - K:
- `k1`
- `k2`
- `k3`
- `k4`
- `kernelMatrix`
- `kernelUnitLength`
- `keyPoints`
- `keySplines`
- `keyTimes` | [
-0.8775255084037781,
0.2547452449798584,
-0.515477180480957,
-0.028597235679626465,
-0.5578135251998901,
-1.2714166641235352,
0.8760401606559753,
0.15370561182498932,
-0.7277483940124512,
-0.385490745306015,
0.1667471081018448,
0.060774065554142,
-0.15070542693138123,
0.4568776488304138,
... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.