file stringlengths 16 94 | text stringlengths 32 24.4k | vector list |
|---|---|---|
http/reference/headers/set-cookie/index.md | HTTP - Headers - Set-Cookie - Examples - Session cookie:
Session cookies are removed when the client shuts down. Cookies are session cookies if they do not specify the `Expires` or `Max-Age` attribute.
Example:
Set-Cookie: sessionId=38afes7a8 | [
-1.0178627967834473,
0.10414643585681915,
-1.2500287294387817,
-0.23497258126735687,
-1.1170352697372437,
-1.1782656908035278,
0.3306795060634613,
1.1786621809005737,
0.17355647683143616,
-0.20531825721263885,
0.6409532427787781,
0.11064538359642029,
-0.7949175834655762,
0.1679825484752655... |
http/reference/headers/set-cookie/index.md | HTTP - Headers - Set-Cookie - Examples - Permanent cookie:
Permanent cookies are removed at a specific date (`Expires`) or after a specific length of time (`Max-Age`) and not when the client is closed.
Example:
Set-Cookie: id=a3fWa; Expires=Wed, 21 Oct 2015 07:28:00 GMT
Example:
Set-Cookie: id=a3fWa; Max-Age=25920... | [
-1.4679608345031738,
-0.1361948847770691,
-0.8751528263092041,
-0.23191654682159424,
-1.1397488117218018,
-1.8770743608474731,
0.027202129364013672,
1.0896016359329224,
0.06884291768074036,
0.24652676284313202,
0.747529923915863,
0.10425469279289246,
-0.6784250140190125,
0.6076449751853943... |
http/reference/headers/set-cookie/index.md | HTTP - Headers - Set-Cookie - Examples - Invalid domains:
A cookie for a domain that does not include the server that set it should be rejected by the user agent.
The following cookie will be rejected if set by a server hosted on `original-company.com`:
Example:
Set-Cookie: qwerty=219ffwef9w0f; Domain=some-company.... | [
-1.1612449884414673,
0.7726892828941345,
-0.4007992744445801,
0.004609491676092148,
-0.15568700432777405,
-0.642478346824646,
0.42425858974456787,
0.4281363785266876,
-0.5838894248008728,
0.38451138138771057,
0.8734233975410461,
-0.12428029626607895,
-0.5970702171325684,
-0.748817145824432... |
http/reference/headers/set-cookie/index.md | HTTP - Headers - Set-Cookie - Examples - Cookie prefixes:
Cookie names prefixed with `__Secure-` or `__Host-` can be used only if they are set with the `Secure` attribute from a secure (HTTPS) origin.
Cookie names prefixed with `__Http-` or `__Host-Http-` can be used only if they are set with the `Secure` attribute f... | [
0.042633965611457825,
0.043504498898983,
-0.4385787844657898,
0.5505431890487671,
-0.3046413064002991,
-0.4335375726222992,
0.35792434215545654,
0.9889401197433472,
-0.2946234941482544,
-0.18616126477718353,
-0.3345358669757843,
0.5597366094589233,
0.14074558019638062,
-0.6424235701560974,... |
http/reference/headers/set-cookie/index.md | HTTP - Headers - Set-Cookie - Examples - Partitioned cookie:
Example:
Set-Cookie: __Host-example=34d8g; SameSite=None; Secure; Path=/; Partitioned;
Note: Partitioned cookies must be set with `Secure`. In addition, it is recommended to use a `__Host` or `__Host-Http-` prefix when setting partitioned cookies to make t... | [
-0.20310284197330475,
0.10605933517217636,
-0.2572762370109558,
0.37618640065193176,
-0.25902971625328064,
-0.971264660358429,
1.3128410577774048,
1.1294848918914795,
-0.8278242349624634,
-0.17861062288284302,
0.32037436962127686,
0.7003195285797119,
-0.2321522980928421,
-0.484496265649795... |
http/reference/headers/content-disposition/index.md | HTTP - Headers - Content-Disposition:
The HTTP `Content-Disposition` header indicates whether content should be displayed inline in the browser as a web page or part of a web page or downloaded as an attachment locally.
In a multipart body, the header must be used on each subpart to provide information about its corr... | [
-0.56968754529953,
-1.8246878385543823,
-0.9186097979545593,
0.6243951320648193,
-0.2301938682794571,
-1.3683538436889648,
0.7724884152412415,
1.1965198516845703,
-0.021293897181749344,
-0.2984869182109833,
-0.4171186089515686,
0.40909087657928467,
-0.8733880519866943,
0.29604092240333557,... |
http/reference/headers/content-disposition/index.md | HTTP - Headers - Content-Disposition - Syntax - As a response header for the main body:
The first parameter in the HTTP context is either `inline` (default value, indicating it can be displayed inside the Web page, or as the Web page) or `attachment` (indicating it should be downloaded; most browsers presenting a 'Sav... | [
-0.48766759037971497,
-0.6280782222747803,
-1.3193159103393555,
1.1963748931884766,
-0.13243159651756287,
-0.978083610534668,
0.9655803442001343,
1.1802940368652344,
-0.3951592743396759,
-0.29302123188972473,
-0.7220385074615479,
0.2946412265300751,
-0.7224974036216736,
0.2494526505470276,... |
http/reference/headers/content-disposition/index.md | HTTP - Headers - Content-Disposition - Syntax - As a header for a multipart body:
A `multipart/form-data` body requires a `Content-Disposition` header to provide information about each subpart of the form (e.g., for every form field and any files that are part of field data). The first directive is always `form-data`,... | [
-0.43272823095321655,
-1.7418608665466309,
-1.2380671501159668,
0.938414990901947,
-0.5036325454711914,
-1.790524959564209,
1.176385521888733,
0.9322458505630493,
-0.09793297946453094,
-0.8333871960639954,
-0.1452268809080124,
-0.47005119919776917,
-0.9823707938194275,
0.7344785332679749,
... |
http/reference/headers/content-disposition/index.md | HTTP - Headers - Content-Disposition - Syntax - As a header for a multipart body - Directives:
- `name`: Is followed by a string containing the name of the HTML field in the form that the content of this subpart refers to. When dealing with multiple files in the same field (for example, the `multiple` attribute of an ... | [
-0.6407397985458374,
-0.4708491563796997,
-1.585339069366455,
0.9255385994911194,
-0.24138514697551727,
-1.6452385187149048,
0.7941189408302307,
-0.1334177702665329,
-0.3076847791671753,
-0.8270279169082642,
-0.6694811582565308,
0.44005346298217773,
-0.5542805790901184,
0.568263053894043,
... |
http/reference/headers/content-disposition/index.md | HTTP - Headers - Content-Disposition - Examples - Triggering download prompt for a resource:
The following response triggers the "Save As" dialog in a browser:
Example:
200 OK
Content-Type: text/html; charset=utf-8
Content-Disposition: attachment; filename="cool.html"
Content-Length: 21
<HTML>Save me!</HTML>
The H... | [
-0.7817683219909668,
-0.3527403473854065,
-0.8051449656486511,
0.6801906228065491,
-0.6340596079826355,
-1.9792557954788208,
1.1405600309371948,
0.7598119378089905,
-1.0015003681182861,
-0.6906760334968567,
0.2262691855430603,
0.2722368836402893,
-0.9461763501167297,
0.02468808740377426,
... |
http/reference/headers/content-disposition/index.md | HTTP - Headers - Content-Disposition - Examples - HTML posting multipart/form-data content type:
The following example shows an HTML form sent using `multipart/form-data` using the `Content-Disposition` header. In practice, the boundary value `delimiter123` would be a browser-generated string like `----872165604191141... | [
-0.9860223531723022,
-1.2422232627868652,
-0.4680899977684021,
0.06852462142705917,
-0.8189197182655334,
-0.7546870708465576,
0.8506906032562256,
1.3313806056976318,
-0.04964688420295715,
-0.2619883120059967,
-0.5455645322799683,
0.8247349262237549,
-0.7758781909942627,
-0.2647366523742676... |
http/reference/headers/link/index.md | HTTP - Headers - Link:
The HTTP `Link` header provides a means for serializing one or more links in HTTP headers. This allows the server to point a client to another resource containing metadata about the requested resource. This header has the same semantics as the HTML `link` element. One benefit of using the `Link`... | [
-1.1434472799301147,
0.1365128606557846,
-1.059332251548767,
0.5788724422454834,
-0.06495806574821472,
-0.4886571764945984,
1.3884692192077637,
1.3602652549743652,
-0.3839983344078064,
-0.573816180229187,
-1.549536943435669,
-0.044306680560112,
-0.46930256485939026,
0.003789655864238739,
... |
http/reference/headers/link/index.md | HTTP - Headers - Link - Syntax:
Example:
Link: <uri-reference>; param1=value1; param2="value2"
- `<uri-reference>`: The URI reference, must be enclosed between `<` and `>` and `percent-encoded`. | [
-0.4629155099391937,
0.10598841309547424,
-0.1868709772825241,
0.5191030502319336,
-1.4178475141525269,
-0.8301537036895752,
1.2442171573638916,
1.2585710287094116,
-0.16324645280838013,
-0.5827969312667847,
-0.7536256313323975,
1.3125677108764648,
0.12023565173149109,
0.04378316551446915,... |
http/reference/headers/link/index.md | HTTP - Headers - Link - Syntax - Parameters:
The link header contains parameters, which are separated with `;` and are equivalent to attributes of the `link` element. Values can be both quoted or unquoted based on field value component rules, so `x=y` is equivalent to `x="y"`. | [
-0.8768553733825684,
-0.08178235590457916,
-1.240685224533081,
0.4382755756378174,
-0.6509453058242798,
-1.370627999305725,
1.6217694282531738,
1.4062103033065796,
-0.08837457001209259,
-0.5936561226844788,
-0.7304133176803589,
-0.01589222252368927,
0.15063594281673431,
0.48529279232025146... |
http/reference/headers/link/index.md | HTTP - Headers - Link - Examples - Enclose URLs in angle brackets:
The URI (absolute or relative) must be enclosed between `<` and `>`:
Example:
Link: <https://example.com>; rel="preconnect"
Example:
Link: https://bad.example; rel="preconnect" | [
-1.5427815914154053,
0.14049464464187622,
0.1696448177099228,
0.4046612083911896,
-1.2456649541854858,
-0.6896633505821228,
1.0687378644943237,
0.532823383808136,
-0.7679543495178223,
-0.058033719658851624,
-1.1249219179153442,
0.26419293880462646,
-0.2078605592250824,
-0.19912968575954437... |
http/reference/headers/link/index.md | HTTP - Headers - Link - Examples - Encoding URLs:
The URI (absolute or relative) must `percent-encode` character codes greater than 255:
Example:
Link: <https://example.com/%E8%8B%97%E6%9D%A1>; rel="preconnect"
Example:
Link: <https://example.com/苗条>; rel="preconnect" | [
-1.1913424730300903,
0.04559960216283798,
0.07736125588417053,
-0.2071150541305542,
-1.0094475746154785,
-1.2238694429397583,
0.5894813537597656,
0.6554027199745178,
-1.3391218185424805,
-0.17814046144485474,
-1.0236616134643555,
0.2058921456336975,
-0.4387473165988922,
-0.300037682056427,... |
http/reference/headers/link/index.md | HTTP - Headers - Link - Examples - Specifying multiple links:
You can specify multiple links separated by commas, for example:
Example:
Link: <https://one.example.com>; rel="preconnect", <https://two.example.com>; rel="preconnect", <https://three.example.com>; rel="preconnect" | [
-0.47128796577453613,
-0.1045580804347992,
-0.9955094456672668,
0.7390726804733276,
-0.5275083184242249,
-0.04555344209074974,
1.023990511894226,
1.7886468172073364,
-1.0648589134216309,
-0.3954492509365082,
-0.6632229685783386,
0.3045012056827545,
-0.28589555621147156,
-0.831279993057251,... |
http/reference/headers/link/index.md | HTTP - Headers - Link - Examples - Pagination through links:
The `Link` header can provide pagination information to a client, which is commonly used to access resources programmatically:
Example:
Link: <https://api.example.com/issues?page=2>; rel="prev", <https://api.example.com/issues?page=4>; rel="next", <https:/... | [
0.018684279173612595,
-0.9355433583259583,
-0.3098146617412567,
0.6582245230674744,
0.07493031024932861,
-0.8410012125968933,
1.287133812904358,
0.656463086605072,
0.1357383131980896,
-0.2009822577238083,
-1.069434404373169,
1.3435076475143433,
-0.08538684993982315,
0.47904396057128906,
... |
http/reference/headers/link/index.md | HTTP - Headers - Link - Examples - Controlling fetch priority:
Even when using `preload` to fetch a resource as early as possible, different types of content will be fetched earlier or later based on the browser's internal prioritization. The `fetchpriority` attribute can be used to hint to the browser that a particul... | [
-0.05737871304154396,
-0.22865784168243408,
-1.0034494400024414,
0.9727507829666138,
-0.7517662048339844,
-0.7038478851318359,
0.7461796998977661,
0.9352244138717651,
0.3805333375930786,
0.09172757714986801,
-0.9219624996185303,
0.0881507396697998,
-1.4878721237182617,
-0.5400760173797607,... |
http/reference/headers/preference-applied/index.md | HTTP - Headers - Preference-Applied:
The HTTP `Preference-Applied` header informs the client about which preferences from the `Prefer` request header were applied by the server.
The server indicates if a preference is applied to a response if it would otherwise be ambiguous for the client. | [
-0.6725190281867981,
-0.6550140976905823,
-1.5547804832458496,
0.9882675409317017,
-0.9781772494316101,
-2.404907703399658,
1.0877004861831665,
0.7780449986457825,
0.21489647030830383,
0.12557342648506165,
-0.8095617294311523,
-0.2525936961174011,
-0.926706850528717,
0.3803815245628357,
... |
http/reference/headers/preference-applied/index.md | HTTP - Headers - Preference-Applied - Syntax:
Example:
Preference-Applied: <preference> | [
0.5997212529182434,
0.27083316445350647,
-1.137956976890564,
0.14844238758087158,
-1.3889622688293457,
-1.1559239625930786,
1.6169711351394653,
1.816744089126587,
0.6479620933532715,
-0.04003656655550003,
-0.6504040956497192,
0.11181184649467468,
-0.6610724329948425,
-0.4693223237991333,
... |
http/reference/headers/preference-applied/index.md | HTTP - Headers - Preference-Applied - Examples - Server applies timezone preferences:
The following request indicates that the client prefers events to be represented in a certain time zone:
Example:
GET /events HTTP/1.1
Host: example.com
Prefer: timezone=America/Los_Angeles
The server supports the preference and s... | [
-0.21361204981803894,
-0.19149181246757507,
-1.2626672983169556,
1.0390958786010742,
-0.8407245874404907,
-2.0161380767822266,
-0.011508578434586525,
0.4486764371395111,
-0.06318739056587219,
0.380750834941864,
0.263206422328949,
0.15735659003257751,
-0.38291221857070923,
-0.12174163013696... |
http/reference/headers/early-data/index.md | HTTP - Headers - Early-Data:
The HTTP `Early-Data` `request header` is set by an intermediary to indicate that the request has been conveyed in TLS early data, and also indicates that the intermediary understands the `425` status code.
If a client has interacted with a server recently, early data (also known as zero ... | [
-0.9108278751373291,
-0.22579191625118256,
-0.9728302955627441,
0.8947042226791382,
-0.5127456784248352,
-1.343318223953247,
0.45371145009994507,
0.1778210699558258,
-0.9826748371124268,
0.5375173687934875,
-0.6415482759475708,
-0.04854203388094902,
-0.698143720626831,
0.1516074687242508,
... |
http/reference/headers/early-data/index.md | HTTP - Headers - Early-Data - Syntax:
Example:
Early-Data: 1 | [
0.3712432086467743,
-0.035039257258176804,
-1.2491750717163086,
-0.11786625534296036,
-1.4166347980499268,
-0.7792840003967285,
1.5103709697723389,
2.3738436698913574,
-0.46402639150619507,
-0.4269108772277832,
-0.3000088632106781,
-0.4235117733478546,
-0.6252015829086304,
-0.5251102447509... |
http/reference/headers/early-data/index.md | HTTP - Headers - Early-Data - Examples - A GET request with an Early-Data header:
A client that wants to use early data can send HTTP requests immediately after sending the TLS `ClientHello`. Sending a request in early data implies that the client is willing to retry a request in response to a `425` status code, so th... | [
0.24063780903816223,
-0.3382128179073334,
-0.8475306034088135,
0.12027023732662201,
0.24154451489448547,
-1.9254252910614014,
-0.03494677320122719,
1.054190993309021,
-0.5256025791168213,
-0.14182142913341522,
-0.463561087846756,
0.24807900190353394,
-0.23652392625808716,
-0.31979668140411... |
http/reference/headers/warning/index.md | HTTP - Headers - Warning:
Deprecated: This feature is no longer recommended.
Note: The header was deprecated because it is not widely generated or surfaced to users (see RFC9111). Some of the information can be inferred from other headers such as `Age`.
The HTTP `Warning` `request` and `response header` contains inf... | [
0.06504669040441513,
0.11862921714782715,
-0.8530398607254028,
-0.2619130313396454,
-0.8868324756622314,
-2.585479974746704,
0.8129920363426208,
1.295121192932129,
-0.28049105405807495,
-0.2886590361595154,
-1.275617241859436,
-0.025773677974939346,
-0.47935745120048523,
0.8632426261901855... |
http/reference/headers/warning/index.md | HTTP - Headers - Warning - Syntax:
Example:
Warning: <warn-code> <warn-agent> <warn-text> [<warn-date>] | [
0.9571332335472107,
0.22261586785316467,
-0.5696256756782532,
-0.7151284217834473,
-1.1844013929367065,
-2.3383214473724365,
0.9307306408882141,
2.1978020668029785,
-0.6176968812942505,
-0.16996042430400848,
-0.8013448715209961,
-0.08417600393295288,
-0.5194079875946045,
-0.453761786222457... |
http/reference/headers/warning/index.md | HTTP - Headers - Warning - Directives:
- `<warn-code>`: A three-digit warning number. The first digit indicates whether the `Warning` is required to be deleted from a stored response after validation.
- `1xx` warn-codes describe the freshness or validation status of the response and will be deleted by a cache after ... | [
-0.46320536732673645,
-0.34569206833839417,
-0.4745584726333618,
0.032927222549915314,
-0.03853157162666321,
-1.072143316268921,
0.4577237069606781,
0.7879126071929932,
-0.39026108384132385,
-0.09510589390993118,
-1.279127836227417,
0.10293014347553253,
-0.43638280034065247,
0.266245365142... |
http/reference/headers/warning/index.md | HTTP - Headers - Warning - Warning codes:
The HTTP Warn Codes registry at iana.org defines the namespace for warning codes.
- Code: 110, Text: Response is Stale, Description: The response provided by a cache is stale (the expiration time set for the response has passed).
- Code: 111, Text: Revalidation Failed, Descri... | [
0.3091503381729126,
-0.19119003415107727,
-0.6000336408615112,
-0.3567558228969574,
-0.105732262134552,
-2.4897634983062744,
1.2464540004730225,
1.2305827140808105,
-1.3300039768218994,
1.1637009382247925,
-0.9534738659858704,
-0.490669310092926,
-0.9732617139816284,
0.9566406011581421,
... |
http/reference/headers/warning/index.md | HTTP - Headers - Warning - Examples:
Example:
Warning: 110 anderson/1.3.37 "Response is stale"
Date: Wed, 21 Oct 2015 07:28:00 GMT
Warning: 112 - "cache down" "Wed, 21 Oct 2015 07:28:00 GMT" | [
0.4782017469406128,
0.06780201196670532,
-0.6048948168754578,
-0.5851919651031494,
-0.6179589033126831,
-2.2909493446350098,
0.6208177208900452,
1.8639768362045288,
-0.5693877935409546,
0.24581408500671387,
-0.352975070476532,
-1.0276761054992676,
-0.42934882640838623,
0.6605008840560913,
... |
http/reference/headers/prefer/index.md | HTTP - Headers - Prefer:
The HTTP `Prefer` header allows clients to indicate preferences for specific server behaviors during request processing.
Note: Browsers have no handling for the `Prefer` and `Preference-Applied` headers: they are used in custom, implementation-specific clients. Ensure both client and server s... | [
-1.0244663953781128,
-0.7520365118980408,
-1.5195366144180298,
1.4057537317276,
-0.7889344096183777,
-1.5508118867874146,
0.5773375034332275,
0.5481012463569641,
0.26635074615478516,
0.029267869889736176,
-0.8533004522323608,
-0.5577574968338013,
-0.8579057455062866,
-0.380349338054657,
... |
http/reference/headers/prefer/index.md | HTTP - Headers - Prefer - Syntax:
Example:
Prefer: <preference>, <preference>, ... | [
0.6153626441955566,
0.1385878473520279,
-0.619317889213562,
0.8746708631515503,
-1.0633989572525024,
-1.2802802324295044,
0.7971363663673401,
1.7452257871627808,
0.7045133113861084,
-0.4918728470802307,
-0.4374934732913971,
-0.0630822405219078,
-1.1885684728622437,
-0.5381293296813965,
-... |
http/reference/headers/prefer/index.md | HTTP - Headers - Prefer - Directives:
- `respond-async`: The client prefers asynchronous processing. For example, the server might respond with `202` response indicated that the request has been accepted, along with the `Location` header that has a URL that the client can use to monitor the state of the processing.
- ... | [
-0.7753896713256836,
-0.577036440372467,
-0.932424783706665,
0.8772574663162231,
-0.9237790703773499,
-1.3121346235275269,
-0.03695359081029892,
0.6000615358352661,
0.5828964710235596,
0.583255410194397,
-0.4098716378211975,
-0.1072433590888977,
-0.4112367331981659,
0.48549169301986694,
... |
http/reference/headers/prefer/index.md | HTTP - Headers - Prefer - Examples - Requesting minimal response:
The following request asks for a minimal response. This is typically a headers-only response (as opposed to `return=representation` where a representation is included in the response body):
Example:
POST /resource HTTP/1.1
Host: example.com
Content-Ty... | [
-1.3909250497817993,
0.1018926352262497,
-0.7749679088592529,
1.0600398778915405,
-0.9802861213684082,
-1.0897011756896973,
0.9760502576828003,
0.0256480872631073,
0.10119596123695374,
-0.29805469512939453,
-0.4479724168777466,
-0.048181161284446716,
-0.2749072313308716,
-0.194385245442390... |
http/reference/headers/prefer/index.md | HTTP - Headers - Prefer - Examples - Requesting asynchronous processing:
This example requests the server start an async processing task:
Example:
POST /process HTTP/1.1
Host: example.com
Prefer: respond-async
{
"task": "check-broken-links"
}
The server responds with a `202` response indicated the request has be... | [
-0.6425171494483948,
-0.3451288044452667,
-0.7405977845191956,
0.997839093208313,
-0.5316866636276245,
-0.5349510312080383,
0.3366338610649109,
0.5854077339172363,
-0.0003582760691642761,
0.20913657546043396,
-0.4235473871231079,
-0.12900744378566742,
0.26786044239997864,
0.397619605064392... |
http/reference/headers/prefer/index.md | HTTP - Headers - Prefer - Examples - Providing multiple preferences:
The following request includes two preferences; `timezone=Jupiter/Red_Spot` indicating a time zone preference for the client, and `handling=strict` for strict validation:
Example:
GET /events HTTP/1.1
Host: example.com
Prefer: handling=strict, time... | [
-1.2491341829299927,
-0.35796576738357544,
-0.8510889410972595,
0.9713422060012817,
-0.5433796644210815,
-1.1666592359542847,
-0.09261307120323181,
0.5406059622764587,
0.05473770201206207,
0.35385459661483765,
-0.4315451979637146,
-0.5669136047363281,
0.05290038138628006,
-0.58182913064956... |
http/reference/headers/permissions-policy/index.md | HTTP - Headers - Permissions-Policy:
The HTTP `Permissions-Policy` `response header` provides a mechanism to allow and deny the use of browser features in a document or within any `iframe` elements in the document.
Violations of a policy can be reported using the Reporting API. Reports may be sent to a server indicat... | [
-0.9173729419708252,
-0.4412616789340973,
-0.7994559407234192,
0.48563700914382935,
-0.9851398468017578,
-1.7789322137832642,
0.41768789291381836,
0.7927754521369934,
0.16193857789039612,
0.44927823543548584,
-1.2496472597122192,
0.4366457462310791,
0.445754736661911,
0.48699241876602173,
... |
http/reference/headers/permissions-policy/index.md | HTTP - Headers - Permissions-Policy - Syntax:
Example:
# Single directive
Permissions-Policy: <directive>=<allowlist>
# Single directive with reporting endpoint
Permissions-Policy: <directive>=<allowlist>;report-to=<endpoint>
# Multiple directives, with and without server reporting endpoints
Permissions-Policy: <di... | [
0.4631749391555786,
-0.7684932351112366,
-0.4147290587425232,
0.31737208366394043,
-0.24692122638225555,
-1.4366209506988525,
0.5114232301712036,
1.2956441640853882,
0.380755752325058,
-0.08385375887155533,
-0.9861953258514404,
0.4624994397163391,
0.08392348885536194,
0.10721264779567719,
... |
http/reference/headers/permissions-policy/index.md | HTTP - Headers - Permissions-Policy - Directives:
- `accelerometer` (experimental): Controls whether the current document is allowed to gather information about the acceleration of the device through the `Accelerometer` interface.
- `ambient-light-sensor` (experimental): Controls whether the current document is allowe... | [
0.5407044887542725,
0.4064662754535675,
-0.3017081916332245,
-0.021990282461047173,
0.041499391198158264,
-0.5173515677452087,
1.0357552766799927,
1.8342034816741943,
-0.7182167768478394,
0.2712191641330719,
-0.2378460317850113,
0.40209007263183594,
0.0554884597659111,
-0.03189386427402496... |
http/reference/headers/permissions-policy/index.md | HTTP - Headers - Permissions-Policy - Examples - Basic usage - Permissions-Policy header:
To allow all origins access to geolocation, you would do this:
Example:
Permissions-Policy: geolocation=*
Or to allow access to a subset of origins, you'd do this:
Example:
Permissions-Policy: geolocation=(self "https://a.ex... | [
-0.29471656680107117,
-1.4384056329727173,
-0.40604498982429504,
0.30996090173721313,
-0.5607711672782898,
-0.674035370349884,
0.26890531182289124,
0.379568874835968,
0.231035053730011,
-0.28631654381752014,
-1.0057356357574463,
0.2924896776676178,
0.5546512007713318,
-0.3288814127445221,
... |
http/reference/headers/permissions-policy/index.md | HTTP - Headers - Permissions-Policy - Examples - Basic usage - iframes:
For an `<iframe>` to have a feature enabled its allowed origin must also be in the allowlist for the parent page. Because of this inheritance behavior, it is a good idea to specify the widest acceptable support for a feature in the HTTP header, an... | [
1.0682775974273682,
-0.8741762042045593,
-0.2894947826862335,
0.3127909004688263,
0.08327503502368927,
-1.5275521278381348,
-0.24204149842262268,
1.2230994701385498,
0.21442610025405884,
-0.38478508591651917,
-1.1495417356491089,
0.5846330523490906,
0.01953081786632538,
0.09404292702674866... |
http/reference/headers/permissions-policy/index.md | HTTP - Headers - Permissions-Policy - Examples - Denying access to powerful features:
SecureCorp Inc. wants to disable Microphone (for example `MediaDevices.getUserMedia()`) and `Geolocation` APIs in its application. It can do so using the following response header:
Example:
Permissions-Policy: microphone=(), geoloc... | [
-1.167036771774292,
-0.23139168322086334,
-0.3322741389274597,
-0.13300561904907227,
-0.8907616138458252,
-0.9244124889373779,
0.5009658336639404,
-0.5298642516136169,
0.6338863372802734,
0.31690776348114014,
-0.43952062726020813,
-0.618025541305542,
0.2502037286758423,
-0.8712040185928345... |
http/reference/headers/permissions-policy/index.md | HTTP - Headers - Permissions-Policy - Examples - Combining HTTP header and `<iframe>` policies:
For example, let's say that we wanted to enable geolocation usage on our own origin, and in embedded content coming from our trusted ad network. We could set up the page-wide Permissions Policy like this:
Example:
Permiss... | [
-0.6255987882614136,
-0.39822566509246826,
-0.18793199956417084,
0.43188005685806274,
-0.6878401637077332,
-1.0328919887542725,
0.7050157785415649,
0.18432402610778809,
0.11545218527317047,
0.7095988392829895,
-0.5739561915397644,
-0.3016807436943054,
0.055501990020275116,
-0.4423864185810... |
http/reference/headers/permissions-policy/index.md | HTTP - Headers - Permissions-Policy - Examples - Reporting violations:
This example shows how to configure reporting of `Permissions-Policy` violations to a server endpoint.
The response headers below block geolocation and define the reporting endpoint name for the feature as "geo_endpoint". The `Reporting-Endpoints`... | [
0.19557473063468933,
-0.4218786656856537,
-0.2433832883834839,
0.23620766401290894,
-0.009241931140422821,
-1.084944248199463,
0.33087754249572754,
0.6213659048080444,
-0.43992334604263306,
-0.040210846811532974,
-0.49491623044013977,
0.5110227465629578,
0.06639460474252701,
0.297594517469... |
http/reference/headers/permissions-policy/loopback-network/index.md | HTTP - Headers - Permissions-Policy - loopback-network:
The HTTP `Permissions-Policy` header `loopback-network` directive controls whether the current document is allowed to make network requests to loopback addresses.
A loopback address is only accessible on the local host; its target will differ on every device. Fo... | [
-1.2447336912155151,
0.24496302008628845,
-0.36986973881721497,
-0.26708489656448364,
-0.5183461904525757,
-1.7456920146942139,
0.37795236706733704,
0.10228362679481506,
-0.6926665902137756,
0.34012940526008606,
-0.8970479965209961,
0.556971549987793,
0.6336082220077515,
0.0666285827755928... |
http/reference/headers/permissions-policy/loopback-network/index.md | HTTP - Headers - Permissions-Policy - loopback-network - Syntax:
Example:
Permissions-Policy: loopback-network=<allowlist>;
- `<allowlist>`: A list of origins for which permission is granted to use the feature. See `Permissions-Policy` > Syntax for more details. | [
-0.7440885901451111,
-0.8510671854019165,
-1.1939942836761475,
-0.14108659327030182,
-0.8591177463531494,
-1.991964340209961,
1.0477174520492554,
1.6031696796417236,
-0.4089329242706299,
0.07480747997760773,
-0.954493522644043,
0.4514433741569519,
0.2289125621318817,
0.07588130235671997,
... |
http/reference/headers/permissions-policy/loopback-network/index.md | HTTP - Headers - Permissions-Policy - loopback-network - Default policy:
The default allowlist for `loopback-network` is `self`. The top-level browsing context and same-origin iframes are allowed access to the `loopback-network` feature by default. | [
-1.2126879692077637,
-1.0242527723312378,
-1.2075804471969604,
0.5902426242828369,
-0.7199484705924988,
-0.5756083726882935,
0.7972071766853333,
1.222324252128601,
-0.6906679272651672,
0.4734976291656494,
-1.0834227800369263,
0.08828370273113251,
0.4923439621925354,
0.7800537943840027,
0... |
http/reference/headers/permissions-policy/loopback-network/index.md | HTTP - Headers - Permissions-Policy - loopback-network - Examples - Basic usage:
SecureCorp Inc. wants to disallow `loopback-network` within all cross-origin iframes except those whose origin is `https://example.com`. It can do so by delivering the following HTTP response header to define a Permissions Policy:
Exampl... | [
-1.4647305011749268,
-0.424823522567749,
-0.9561058878898621,
0.35107603669166565,
-0.6194073557853699,
-1.2906092405319214,
0.6083935499191284,
0.6742650270462036,
-1.1060653924942017,
0.5850222706794739,
-0.6374179720878601,
-0.5738382339477539,
-0.18565090000629425,
-1.0160906314849854,... |
http/reference/headers/permissions-policy/loopback-network/index.md | HTTP - Headers - Permissions-Policy - loopback-network - Examples - Using the default policy:
If an allowlist for `loopback-network` is not defined by a `Permissions-Policy` response header, user agents will apply the default allowlist `self`. In this mode, `loopback-network` is automatically allowed in the top-level ... | [
-1.0391350984573364,
-0.6920022964477539,
-1.670829176902771,
0.8752214908599854,
-0.8547928333282471,
-0.5393279194831848,
1.0530043840408325,
1.2856636047363281,
-1.0040826797485352,
0.49700427055358887,
-1.3222664594650269,
-0.35172775387763977,
0.49625325202941895,
0.33933568000793457,... |
http/reference/headers/permissions-policy/local-network-access/index.md | HTTP - Headers - Permissions-Policy - local-network-access:
The HTTP `Permissions-Policy` header `local-network-access` directive controls whether the current document is allowed to make network requests to local and loopback addresses. This policy directive is an alias for the newer `local-network` and `loopback-netw... | [
0.6074181199073792,
-0.09027443081140518,
-0.038627058267593384,
-0.6889020800590515,
0.3447132706642151,
-1.6578372716903687,
0.5455036759376526,
0.22092343866825104,
0.7422981858253479,
-0.020418673753738403,
-0.9011041522026062,
0.5819623470306396,
-0.2121444195508957,
-0.25430947542190... |
http/reference/headers/permissions-policy/local-network-access/index.md | HTTP - Headers - Permissions-Policy - local-network-access - Syntax:
Example:
Permissions-Policy: local-network-access=<allowlist>;
- `<allowlist>`: A list of origins for which permission is granted to use the feature. See `Permissions-Policy` > Syntax for more details. | [
-0.3400588631629944,
-0.3443347215652466,
-0.8601830005645752,
-0.4904460906982422,
-0.5378431081771851,
-2.123011827468872,
1.011361837387085,
0.8889604806900024,
0.14273352921009064,
0.44303998351097107,
-0.6050366163253784,
0.461198091506958,
0.060340747237205505,
-0.24416260421276093,
... |
http/reference/headers/permissions-policy/local-network-access/index.md | HTTP - Headers - Permissions-Policy - local-network-access - Default policy:
The default allowlist for `local-network-access` is `self`. | [
-0.1208486258983612,
-0.38044849038124084,
-1.1491682529449463,
-0.2225693017244339,
-0.7137166857719421,
-1.0048587322235107,
0.8381615877151489,
0.2888614535331726,
0.35468125343322754,
0.6164461970329285,
-0.7833042144775391,
-0.02135526016354561,
0.27799421548843384,
-0.360167980194091... |
http/reference/headers/permissions-policy/local-network/index.md | HTTP - Headers - Permissions-Policy - local-network:
The HTTP `Permissions-Policy` header `local-network` directive controls whether the current document is allowed to make network requests to local addresses.
A local address is only accessible on the local network; its target will differ on different networks. For e... | [
-0.5380606651306152,
0.3042352497577667,
-0.23188196122646332,
-0.35547149181365967,
-0.3242282271385193,
-1.72480046749115,
0.5052742958068848,
-0.2121710628271103,
0.11386503279209137,
0.16851715743541718,
-0.9796363711357117,
0.2620541453361511,
0.3206850290298462,
-0.6109721064567566,
... |
http/reference/headers/permissions-policy/local-network/index.md | HTTP - Headers - Permissions-Policy - local-network - Syntax:
Example:
Permissions-Policy: local-network=<allowlist>;
- `<allowlist>`: A list of origins for which permission is granted to use the feature. See `Permissions-Policy` > Syntax for more details. | [
-0.18022087216377258,
-0.4097695052623749,
-1.0444427728652954,
-0.38344404101371765,
-0.5484869480133057,
-2.084813117980957,
0.9407885670661926,
1.171457052230835,
0.23742106556892395,
0.09250074625015259,
-0.8181114792823792,
0.7061820030212402,
0.0265531986951828,
-0.38462838530540466,... |
http/reference/headers/permissions-policy/local-network/index.md | HTTP - Headers - Permissions-Policy - local-network - Default policy:
The default allowlist for `local-network` is `self`. The top-level browsing context and same-origin iframes are allowed access to the `local-network` feature by default. | [
-0.3349969685077667,
-0.7906151413917542,
-1.0791735649108887,
0.355965793132782,
-0.37999019026756287,
-0.6659610271453857,
0.896848201751709,
0.4809495210647583,
0.2277643382549286,
0.4225709140300751,
-0.9123247861862183,
0.126664936542511,
0.37847277522087097,
0.30553194880485535,
0.... |
http/reference/headers/permissions-policy/local-network/index.md | HTTP - Headers - Permissions-Policy - local-network - Examples - Basic usage:
SecureCorp Inc. wants to disallow `local-network` within all cross-origin iframes except those whose origin is `https://example.com`. It can do so by delivering the following HTTP response header to define a Permissions Policy:
Example:
Pe... | [
0.3201809227466583,
-0.4451066851615906,
-0.10615304112434387,
0.36997735500335693,
-0.016693003475666046,
-1.2288187742233276,
0.477863609790802,
0.9007948637008667,
-0.017822928726673126,
-0.2092905342578888,
-0.5786975026130676,
0.7254963517189026,
0.2930998206138611,
-0.629187524318695... |
http/reference/headers/permissions-policy/local-network/index.md | HTTP - Headers - Permissions-Policy - local-network - Examples - Using the default policy:
If an allowlist for `local-network` is not defined by a `Permissions-Policy` response header, user agents will apply the default allowlist `self`. In this mode, `local-network` is automatically allowed in the top-level browsing ... | [
0.06024378910660744,
-0.609505832195282,
-0.4586779475212097,
0.7090093493461609,
-0.05626148357987404,
-1.1484758853912354,
0.025193344801664352,
1.0117026567459106,
0.11443281173706055,
0.0033151479437947273,
-1.0062828063964844,
-0.005405370146036148,
0.75809246301651,
0.251487672328949... |
http/reference/headers/attribution-reporting-register-source/index.md | HTTP - Headers - Attribution-Reporting-Register-Source:
Deprecated: This feature is no longer recommended. Non-standard: This feature is not standardized.
The HTTP `Attribution-Reporting-Register-Source` `response header` registers a page feature as an attribution source. This header is included as part of a response... | [
-0.5212174654006958,
-0.5547820925712585,
-0.8667191863059998,
0.28114959597587585,
-0.829613208770752,
-1.2386037111282349,
0.7463436126708984,
1.1328535079956055,
1.1783976554870605,
-0.25873953104019165,
-0.5073333978652954,
0.5501581430435181,
-0.08506354689598083,
0.41440412402153015,... |
http/reference/headers/attribution-reporting-register-source/index.md | HTTP - Headers - Attribution-Reporting-Register-Source - Syntax:
Example:
Attribution-Reporting-Register-Source: <json-string> | [
-0.605170488357544,
-0.365048348903656,
-0.7956718802452087,
-0.18609432876110077,
-0.9089140295982361,
-0.9901213049888611,
0.977463960647583,
1.6258339881896973,
0.6848480105400085,
-0.17371320724487305,
-0.18967925012111664,
0.5497739315032959,
-0.43125981092453003,
-0.36245468258857727... |
http/reference/headers/attribution-reporting-register-source/index.md | HTTP - Headers - Attribution-Reporting-Register-Source - Directives:
- `<json-string>`: A JSON string providing the information that the browser should store when the attribution source is interacted with. Available fields are as follows:
- `"source_event_id"` (optional): A string representing an ID for the attribut... | [
0.4907824993133545,
-0.07601431012153625,
-0.3232611119747162,
0.27803996205329895,
0.2580927312374115,
-0.7996838092803955,
0.9010820984840393,
1.4912029504776,
-0.12530720233917236,
0.39377859234809875,
0.0036821775138378143,
0.6804603338241577,
-0.2893899083137512,
0.6301413178443909,
... |
http/reference/headers/attribution-reporting-register-source/index.md | HTTP - Headers - Attribution-Reporting-Register-Source - Examples - Registering a source for an event-level report:
A Node.js server might set the `Attribution-Reporting-Register-Source` response header as follows to make a browser generate an event-level report when a trigger is matched to a source:
Example:
res.se... | [
-0.8024811744689941,
-0.37543633580207825,
-0.917564332485199,
0.8580856323242188,
-0.6359573602676392,
-0.8737646341323853,
0.06176868826150894,
0.460999995470047,
0.5730425715446472,
0.09022816270589828,
0.3947776257991791,
1.0888869762420654,
-0.5977553129196167,
0.6454054117202759,
0... |
http/reference/headers/attribution-reporting-register-source/index.md | HTTP - Headers - Attribution-Reporting-Register-Source - Examples - Registering a source for a summary report:
To make the browser generate a summary report when a trigger is matched to a source, you need to include some extra fields, in addition to those required for event-level report generation.
Example:
res.set(... | [
-0.967318594455719,
-0.24791981279850006,
-1.1018502712249756,
-0.07299153506755829,
-0.6680968403816223,
-1.5314399003982544,
-0.06676006317138672,
0.719511091709137,
-0.13565444946289062,
0.8371796607971191,
0.274455726146698,
0.9435131549835205,
0.0008856989443302155,
0.0896417796611785... |
http/reference/headers/no-vary-search/index.md | HTTP - Headers - No-Vary-Search:
The HTTP `No-Vary-Search` `response header` specifies a set of rules that define how a URL's query parameters will affect cache matching. These rules dictate whether the same URL with different URL parameters should be saved as separate browser cache entries.
This allows the browser t... | [
-0.48073646426200867,
-0.7295287847518921,
-1.3017991781234741,
1.0324020385742188,
-0.6008153557777405,
-1.158227562904358,
0.8676081895828247,
1.101232886314392,
-0.5272802114486694,
-0.35586655139923096,
-0.8862649202346802,
-0.5352911949157715,
-0.8402894139289856,
0.11309586465358734,... |
http/reference/headers/no-vary-search/index.md | HTTP - Headers - No-Vary-Search - Syntax:
Example:
No-Vary-Search: key-order
No-Vary-Search: params
No-Vary-Search: params=("param1" "param2")
No-Vary-Search: params, except=("param1" "param2")
No-Vary-Search: key-order, params, except=("param1") | [
-0.07806672155857086,
-0.39541319012641907,
-0.8982155323028564,
0.2780779302120209,
-1.0717809200286865,
-0.3587445318698883,
0.3527361750602722,
1.9525461196899414,
0.06589686870574951,
-0.3980916142463684,
-0.34362658858299255,
-1.0307213068008423,
-0.29699891805648804,
-0.1031287163496... |
http/reference/headers/no-vary-search/index.md | HTTP - Headers - No-Vary-Search - Directives:
- `key-order` (optional): Indicates that URLs will not be cached as separate entries if the order in which parameters appear in the URL is the only difference. The presence of other parameters will cause URLs to be cached separately.
- `params` (optional): Either a boolean... | [
-0.17318062484264374,
-0.42599621415138245,
-1.0962544679641724,
0.7771289944648743,
-0.847227931022644,
-1.0202807188034058,
0.2843991816043854,
0.6899584531784058,
-0.2492564171552658,
0.4241260886192322,
-0.36661624908447266,
-0.3360776901245117,
-0.3642704486846924,
-0.1292103528976440... |
http/reference/headers/no-vary-search/index.md | HTTP - Headers - No-Vary-Search - Description - Relationship with the Speculation Rules API:
The Speculation Rules API supports using the `No-Vary-Search` header to reuse an existing prefetched or prerendered page for different URL parameters — if they are included in the `No-Vary-Search` header.
Warning: Additional ... | [
-0.4660026729106903,
-0.20828278362751007,
-1.3717776536941528,
1.4502501487731934,
-0.8012683391571045,
-0.6214800477027893,
0.6260784268379211,
0.8697136044502258,
-0.008445784449577332,
0.12821392714977264,
-0.44006627798080444,
0.39233967661857605,
-0.18612000346183777,
0.2610739171504... |
http/reference/headers/no-vary-search/index.md | HTTP - Headers - No-Vary-Search - Examples - Allowing responses from URLs with differently ordered params to match the same cache entry:
If you have for example a search page that stores its search criteria in URL parameters, and you can't guarantee that the parameters will be added to the URL in the same order each t... | [
0.1157832071185112,
-0.062217000871896744,
-1.5425786972045898,
0.8233837485313416,
-0.9067961573600769,
-0.10220301151275635,
0.961435854434967,
1.0030841827392578,
-0.5095311403274536,
-0.07027167081832886,
-0.6342600584030151,
-0.5561196208000183,
-0.4156949818134308,
0.4993863701820373... |
http/reference/headers/no-vary-search/index.md | HTTP - Headers - No-Vary-Search - Examples - Allowing responses from URLs with a different param to match the same cache entry:
Consider a case where a user directory landing page, `/users`, has already been cached. An `id` parameter might be used to bring up information on a specific user, for example `/users?id=345`... | [
0.9007800221443176,
-0.43789228796958923,
-1.2081501483917236,
0.4196361303329468,
-0.29753023386001587,
-1.39739191532135,
0.6364970207214355,
0.6592347025871277,
-0.5353498458862305,
0.00032568536698818207,
-0.7689936757087708,
0.37264516949653625,
0.07297643274068832,
0.1611342877149582... |
http/reference/headers/no-vary-search/index.md | HTTP - Headers - No-Vary-Search - Examples - Allowing responses from URLs with multiple different params to match the same cache entry:
Say you also had URL parameters that sorted the list of users on the page in ascending or descending alphabetical order, and specified the language to display the UI strings in, for e... | [
-0.0058053163811564445,
-0.4249643087387085,
-0.6111055612564087,
0.9200197458267212,
-0.3807685673236847,
-0.5816138982772827,
1.404583215713501,
0.5698102712631226,
-0.5744785070419312,
-0.36711543798446655,
-0.44160887598991394,
-0.0361902192234993,
0.0990762859582901,
-0.04431307315826... |
http/reference/headers/no-vary-search/index.md | HTTP - Headers - No-Vary-Search - Examples - Specifying params that do cause cache matching misses:
Say the app behaved differently, with `/users` pointing to the main user directory landing page and `/users?id=345` pointing to a completely separate detail page for a specific user. In this case you would want the brow... | [
0.25196224451065063,
-0.6096323728561401,
-1.8047319650650024,
0.017188597470521927,
-0.7380136847496033,
-0.8580002784729004,
0.85293048620224,
0.9918017387390137,
-1.796717882156372,
-0.016849663108587265,
-0.48280996084213257,
-1.6579080820083618,
-0.2663669288158417,
0.0543806180357933... |
http/reference/headers/attribution-reporting-register-trigger/index.md | HTTP - Headers - Attribution-Reporting-Register-Trigger:
Deprecated: This feature is no longer recommended. Non-standard: This feature is not standardized.
The HTTP `Attribution-Reporting-Register-Trigger` `response header` registers a page feature as an attribution trigger. This header is included as part of a respo... | [
-0.43307262659072876,
-0.45103251934051514,
-0.6794902086257935,
0.01969185471534729,
-1.156681776046753,
-1.2604342699050903,
1.2630287408828735,
1.1887260675430298,
0.35362520813941956,
0.22774136066436768,
-0.5032230615615845,
0.34076082706451416,
0.028948478400707245,
0.825785040855407... |
http/reference/headers/attribution-reporting-register-trigger/index.md | HTTP - Headers - Attribution-Reporting-Register-Trigger - Syntax:
Example:
Attribution-Reporting-Register-Trigger: <json-string> | [
-0.17947924137115479,
-0.09642980247735977,
-0.6746983528137207,
-0.02125164493918419,
-1.0404869318008423,
-0.7667055130004883,
1.0068155527114868,
1.5201243162155151,
0.301623672246933,
0.25445371866226196,
-0.21477031707763672,
0.3509528636932373,
-0.7021613121032715,
-0.475295245647430... |
http/reference/headers/attribution-reporting-register-trigger/index.md | HTTP - Headers - Attribution-Reporting-Register-Trigger - Directives:
- `<json-string>`: A JSON string providing data that can be included in generated reports, such as the ID of the trigger, and priority and deduplication values. Available fields are as follows:
- `"aggregatable_trigger_data"`: An array of objects,... | [
0.9496622681617737,
-0.5035740733146667,
-0.33679497241973877,
0.7819646000862122,
0.5267794728279114,
-1.3292343616485596,
0.5870801210403442,
1.2464385032653809,
-0.5432384610176086,
0.36313536763191223,
-0.07972682267427444,
0.8939908742904663,
-0.41628971695899963,
0.10956472158432007,... |
http/reference/headers/attribution-reporting-register-trigger/index.md | HTTP - Headers - Attribution-Reporting-Register-Trigger - Examples - Registering a trigger for an event-level report:
A Node.js server might set the `Attribution-Reporting-Register-Trigger` response header as follows to register a trigger intended to match an event-level report attribution source:
Example:
res.set(
... | [
-0.5346893072128296,
-0.31915438175201416,
-0.616767942905426,
0.8904558420181274,
-0.9404765367507935,
-0.6911638379096985,
0.7236999273300171,
0.38500964641571045,
0.08295778930187225,
0.17881518602371216,
0.24567630887031555,
0.5916094779968262,
-0.6069914698600769,
0.7783731818199158,
... |
http/reference/headers/attribution-reporting-register-trigger/index.md | HTTP - Headers - Attribution-Reporting-Register-Trigger - Examples - Registering a trigger for a summary report:
When registering a trigger intended to match with a summary report attribution source, you need to include the following fields:
Example:
res.set(
"Attribution-Reporting-Register-Trigger",
JSON.string... | [
-0.9023529887199402,
-0.11194576323032379,
-0.7776932120323181,
-0.12603583931922913,
-0.781265914440155,
-1.858343243598938,
0.16121235489845276,
0.5273433923721313,
-0.5731536746025085,
0.6441527009010315,
0.20438776910305023,
0.39534398913383484,
-0.11737427115440369,
0.1977610290050506... |
http/reference/methods/delete/index.md | HTTP - Methods - DELETE:
The `DELETE` HTTP method asks the server to delete a specified resource.
Requests using `DELETE` should only be used to delete data and shouldn't contain a body.
Note: The semantics of sending a message body in `DELETE` requests are undefined. Some servers may reject the request with a 4XX c... | [
-0.7538718581199646,
0.32592347264289856,
-0.5730085372924805,
0.368898868560791,
-0.4067482352256775,
-1.9296211004257202,
0.5655474066734314,
0.1535450965166092,
-0.3884170651435852,
-0.6287755370140076,
-0.0044478680938482285,
0.40980103611946106,
-0.5983366966247559,
-0.059494722634553... |
http/reference/methods/delete/index.md | HTTP - Methods - DELETE - Syntax:
Example:
DELETE <request-target>["?"<query>] HTTP/1.1
- `<request-target>`: Identifies the target resource of the request when combined with the information provided in the `Host` header. This is an absolute path (e.g., `/path/to/file.html`) in requests to an origin server, and an a... | [
-0.31132712960243225,
0.07583264261484146,
-0.8731913566589355,
0.6320410370826721,
0.040055274963378906,
-1.785700798034668,
1.437608003616333,
-0.16063183546066284,
-0.23310495913028717,
0.03311232104897499,
-0.2295321673154831,
0.2144155204296112,
-0.824276864528656,
0.3656409978866577,... |
http/reference/methods/delete/index.md | HTTP - Methods - DELETE - Examples - Successfully deleting a resource:
The following request asks the server to delete the resource `file.html`:
Example:
DELETE /file.html HTTP/1.1
Host: example.com
If the request is successful, there are several possible successful response status codes. A `204` response means the... | [
-1.2261693477630615,
0.6432265639305115,
-0.4895656108856201,
0.163081094622612,
-0.19285085797309875,
-1.8186252117156982,
0.4979786276817322,
-0.01337621733546257,
-0.5487029552459717,
0.11470310389995575,
-0.04313792288303375,
0.8822874426841736,
-0.4217188358306885,
0.3641979694366455,... |
http/reference/methods/put/index.md | HTTP - Methods - PUT:
The `PUT` HTTP method creates a new resource or replaces a representation of the target resource with the request `content`.
The difference between `PUT` and `POST` is that `PUT` is `idempotent`: calling it once is no different from calling it several times successively (there are no side effect... | [
-0.511550784111023,
-0.5239080190658569,
-0.684292733669281,
1.1020445823669434,
-0.2853506803512573,
-1.8858318328857422,
-0.19017238914966583,
1.0672744512557983,
0.19126728177070618,
-0.25825077295303345,
-0.30018559098243713,
0.8612228631973267,
0.279642254114151,
-0.12255589663982391,... |
http/reference/methods/put/index.md | HTTP - Methods - PUT - Syntax:
Example:
PUT <request-target>["?"<query>] HTTP/1.1
- `<request-target>`: Identifies the target resource of the request when combined with the information provided in the `Host` header. This is an absolute path (e.g., `/path/to/file.html`) in requests to an origin server, and an absolut... | [
-0.5608601570129395,
0.21329492330551147,
-1.1611411571502686,
0.9299883842468262,
-0.17395810782909393,
-1.3112211227416992,
0.7449280023574829,
0.071987085044384,
-0.25046682357788086,
0.0938693955540657,
-0.41467443108558655,
0.4640427231788635,
-0.17099496722221375,
-0.0506035387516021... |
http/reference/methods/put/index.md | HTTP - Methods - PUT - Examples - Successfully creating a resource:
The following `PUT` request asks to create a resource at `example.com/new.html` with the content `<p>New File</p>`:
Example:
PUT /new.html HTTP/1.1
Host: example.com
Content-type: text/html
Content-length: 16
<p>New File</p>
If the target resource... | [
-0.6192048192024231,
-0.07371249049901962,
-0.4345475435256958,
1.04667329788208,
-0.24044817686080933,
-0.7241966128349304,
-0.09234447032213211,
0.7802753448486328,
-0.5278834700584412,
-0.016126351431012154,
0.5183225870132446,
0.5902564525604248,
-0.013513602316379547,
-0.2573654055595... |
http/reference/methods/patch/index.md | HTTP - Methods - PATCH:
The `PATCH` HTTP method applies partial modifications to a resource.
`PATCH` is somewhat analogous to the "update" concept found in `CRUD` (in general, HTTP is different than `CRUD`, and the two should not be confused).
In comparison with `PUT`, a `PATCH` serves as a set of instructions for m... | [
-0.26871734857559204,
-0.507640540599823,
-0.7114381194114685,
0.878254234790802,
-0.19577986001968384,
-2.5476815700531006,
1.7862077951431274,
0.9239987730979919,
-0.2895219922065735,
0.06535330414772034,
-0.3308725655078888,
0.47176045179367065,
-0.5965865254402161,
0.48115235567092896,... |
http/reference/methods/patch/index.md | HTTP - Methods - PATCH - Syntax:
Example:
PATCH <request-target>["?"<query>] HTTP/1.1
- `<request-target>`: Identifies the target resource of the request when combined with the information provided in the `Host` header. This is an absolute path (e.g., `/path/to/file.html`) in requests to an origin server, and an abs... | [
0.01608620584011078,
-0.1309879720211029,
-1.045578122138977,
0.7097089290618896,
0.05449692904949188,
-1.6439793109893799,
1.8715245723724365,
0.002561597153544426,
-0.8218706846237183,
0.3808082938194275,
-0.14392395317554474,
0.42823734879493713,
-0.705778181552887,
0.3044179379940033,
... |
http/reference/methods/patch/index.md | HTTP - Methods - PATCH - Examples - Successfully modifying a resource:
Assume there is a resource on the server representing a user with a numeric ID of `123` in the following format:
Example:
{
"firstName": "Example",
"LastName": "User",
"userId": 123,
"signupDate": "2024-09-09T21:48:58Z",
"status": "acti... | [
0.5103986263275146,
-0.8342201709747314,
-0.3844150900840759,
0.32004326581954956,
0.5322602987289429,
-1.2460658550262451,
0.5431491732597351,
1.2866411209106445,
-0.2139396369457245,
-0.08303342014551163,
-0.6962851285934448,
0.7632767558097839,
0.11924868822097778,
-0.1583917886018753,
... |
http/reference/methods/trace/index.md | HTTP - Methods - TRACE:
The `TRACE` HTTP method performs a message loop-back test along the path to the target resource.
The final recipient of the request should reflect the message as received (excluding any fields that might include sensitive data) back to the client as the message body of a `200` response with a ... | [
-0.9050858616828918,
-0.6088806986808777,
-0.9036538600921631,
0.4262029230594635,
0.2804316580295563,
-1.1553828716278076,
1.0525786876678467,
-0.09230571985244751,
-1.374129295349121,
0.2774886190891266,
-0.02746291644871235,
1.2645236253738403,
0.21553407609462738,
0.1441531926393509,
... |
http/reference/methods/trace/index.md | HTTP - Methods - TRACE - Syntax:
Example:
TRACE <request-target>["?"<query>] HTTP/1.1
- `<request-target>`: Identifies the target resource of the request when combined with the information provided in the `Host` header. This is an absolute path (e.g., `/path/to/file.html`) in requests to an origin server, and an abs... | [
-0.07890967279672623,
-0.045291315764188766,
-1.1334491968154907,
0.9076437950134277,
0.42231959104537964,
-1.6778836250305176,
1.4300497770309448,
-0.10054542869329453,
-0.701050877571106,
0.41764548420906067,
-0.249905064702034,
0.09121282398700714,
-0.22354239225387573,
0.29419222474098... |
http/reference/methods/trace/index.md | HTTP - Methods - TRACE - Examples - Successful TRACE request:
A `TRACE` request can be performed using `curl`:
Example:
curl -v -X TRACE example.com
This produces the following HTTP request:
Example:
TRACE / HTTP/1.1
Host: example.com
User-Agent: curl/8.7.1
Accept: */*
A `200` response with the request headers c... | [
-1.0600942373275757,
0.478115975856781,
-0.31262826919555664,
0.3231601119041443,
-0.308871328830719,
-0.8982345461845398,
0.21298959851264954,
-0.15711304545402527,
-1.4231460094451904,
0.059723179787397385,
0.448913037776947,
0.3789544105529785,
0.4649142324924469,
-0.05985153838992119,
... |
http/reference/status/205/index.md | HTTP - Status - 205:
The HTTP `205 Reset Content` successful response status code indicates that the request has been successfully processed and the client should reset the document view.
This response is intended to support use cases where the user receives content that supports data entry, submits user-edited data ... | [
-0.6742427349090576,
0.32167887687683105,
-0.2883322536945343,
-0.09050217270851135,
0.2136053442955017,
-1.2033792734146118,
0.8422815203666687,
0.9107369184494019,
-0.3228164315223694,
0.4106959104537964,
-0.6799349784851074,
0.30086469650268555,
-0.14976488053798676,
0.6436020731925964,... |
http/reference/status/205/index.md | HTTP - Status - 205 - Status:
Example:
205 Reset Content | [
0.10992138832807541,
0.21327361464500427,
-0.9421559572219849,
-0.8770526051521301,
-1.5944193601608276,
0.37365037202835083,
1.7056306600570679,
2.174468517303467,
-0.6207032203674316,
-0.3141741156578064,
-0.43964752554893494,
1.3663114309310913,
-0.38752245903015137,
0.2494128942489624,... |
http/reference/status/205/index.md | HTTP - Status - 205 - Examples - Resetting a form after receiving a `205 Reset Content`:
The client in this example sends a `POST` request to submit a form with the comment `Hello!`:
Example:
POST /submit HTTP/1.1
Host: example.com
Content-Type: application/x-www-form-urlencoded
Content-Length: 16
comment=Hello%21
... | [
-1.0906929969787598,
0.1241995096206665,
-0.07506127655506134,
0.029036156833171844,
-0.6640874743461609,
-1.3459157943725586,
0.6803954243659973,
1.0836255550384521,
-1.025834083557129,
-0.22413098812103271,
-0.05725378543138504,
0.9640415906906128,
0.08016891032457352,
0.2968662977218628... |
http/reference/status/418/index.md | HTTP - Status - 418:
The HTTP `418 I'm a teapot` status response code indicates that the server refuses to brew coffee because it is, permanently, a teapot. A combined coffee/tea pot that is temporarily out of coffee should instead return `503`. This error is a reference to Hyper Text Coffee Pot Control Protocol defin... | [
-0.31602832674980164,
-0.21218368411064148,
-0.7339754700660706,
-0.06629996746778488,
-0.4026379883289337,
-2.505791425704956,
0.0714758038520813,
0.9169629812240601,
0.29676729440689087,
0.6676174402236938,
-0.8106333613395691,
-0.06850671023130417,
0.4055942893028259,
0.1658150404691696... |
http/reference/status/418/index.md | HTTP - Status - 418 - Status:
Example:
418 I'm a teapot | [
0.5695405006408691,
0.3287719190120697,
-1.5633268356323242,
-0.4526852071285248,
-0.8233537673950195,
-1.416603446006775,
0.4794982671737671,
1.3950854539871216,
0.8613891005516052,
0.41821369528770447,
-0.23017911612987518,
0.24973586201667786,
-0.10648749023675919,
-0.2140451967716217,
... |
http/reference/status/303/index.md | HTTP - Status - 303:
The HTTP `303 See Other` redirection response status code indicates that the browser should redirect to the URL in the `Location` header instead of rendering the requested resource.
This response code is often sent back as a result of `PUT` or `POST` methods so the client may retrieve a confirmat... | [
-2.0607857704162598,
-0.26509198546409607,
-0.7722907066345215,
-0.6737259030342102,
-0.451762855052948,
-1.3425885438919067,
0.36616694927215576,
0.5785320401191711,
0.31220319867134094,
0.5978547930717468,
-0.795074999332428,
0.2747778296470642,
0.09669286012649536,
0.22708523273468018,
... |
http/reference/status/303/index.md | HTTP - Status - 303 - Status:
Example:
303 See Other | [
-0.4817631244659424,
-0.09014426171779633,
-0.8351249694824219,
-1.167590618133545,
-1.127134084701538,
0.022781696170568466,
1.217846155166626,
1.5905818939208984,
-0.2171403020620346,
0.1082296371459961,
0.05934529006481171,
0.37094148993492126,
0.5666746497154236,
-0.42411962151527405,
... |
http/reference/status/303/index.md | HTTP - Status - 303 - Examples - 303 response on form submission:
The client in this example sends a `POST` request to submit a form to a generic subscription.
Example:
POST /subscribe HTTP/1.1
Host: example.com
Content-Type: application/x-www-form-urlencoded
Content-Length: 50
name=Brian%20Smith&email=brian.smith%... | [
-2.0299549102783203,
-0.6606862545013428,
-0.3671762943267822,
-1.3563164472579956,
0.09792688488960266,
-1.6150795221328735,
0.9532061219215393,
0.055526018142700195,
-0.1196276992559433,
0.3012716770172119,
-0.10340765118598938,
0.6459599137306213,
0.08495036512613297,
-0.174881815910339... |
http/reference/status/409/index.md | HTTP - Status - 409:
The HTTP `409 Conflict` client error response status code indicates a request conflict with the current state of the target resource.
In `WebDAV` remote web authoring, 409 conflict responses are errors sent to the client so that a user might be able to resolve a conflict and resubmit the request.... | [
-0.8673556447029114,
-0.28543803095817566,
-0.6047636270523071,
-0.4181022346019745,
0.12103940546512604,
-0.7371209859848022,
0.5816631317138672,
0.8154717087745667,
0.23287788033485413,
-0.004131436347961426,
0.2756696343421936,
0.41679641604423523,
-0.880233883857727,
0.4598408341407776... |
http/reference/status/409/index.md | HTTP - Status - 409 - Status:
Example:
409 Conflict | [
0.5144338011741638,
0.26362699270248413,
-0.48358452320098877,
-0.950697660446167,
-0.9047296047210693,
0.49890661239624023,
1.0318115949630737,
1.9193098545074463,
0.42713993787765503,
-0.183818519115448,
0.3078373968601227,
0.27139467000961304,
-0.7616596817970276,
0.20977869629859924,
... |
http/reference/status/409/index.md | HTTP - Status - 409 - Examples - Concurrent tasks disallowed:
In the following example, we want to kick off an automation process that performs a common task in the system:
Example:
POST /tasks HTTP/1.1
Host: example.com
Content-Type: application/json
{
"task": "emailDogOwners",
"template": "pickup"
}
In this ... | [
-0.3783528506755829,
-0.1570337563753128,
-0.4637663960456848,
0.9528763890266418,
0.4594219923019409,
-0.5772879123687744,
0.1097160279750824,
1.130776047706604,
0.010877177119255066,
0.30218589305877686,
-0.6112831830978394,
0.3731294572353363,
0.3696141242980957,
0.12968100607395172,
... |
http/reference/status/401/index.md | HTTP - Status - 401:
The HTTP `401 Unauthorized` client error response status code indicates that a request was not successful because it lacks valid authentication credentials for the requested resource. This status code is sent with an HTTP `WWW-Authenticate` response header that contains information on the authenti... | [
-0.9002531170845032,
0.704858660697937,
-0.4853120446205139,
-0.859010636806488,
0.19458118081092834,
-0.9653748273849487,
0.12273357808589935,
0.4320732355117798,
-0.7396790981292725,
0.9604820013046265,
-0.23453202843666077,
-0.14350366592407227,
-0.17941321432590485,
-0.2639607191085815... |
http/reference/status/401/index.md | HTTP - Status - 401 - Status:
Example:
401 Unauthorized | [
0.14938132464885712,
0.9322525262832642,
-0.6662413477897644,
-0.5282140970230103,
-0.9845513105392456,
0.5074962377548218,
0.8712158799171448,
1.9831445217132568,
0.4309678077697754,
0.6704636216163635,
-0.18352976441383362,
0.16068585216999054,
-0.133062481880188,
-0.5773698687553406,
... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.