About: HTTP location     Goto   Sponge   NotDistinct   Permalink

An Entity of Type : yago:Text106387980, within Data Space : dbpedia.org associated with source document(s)
QRcode icon
http://dbpedia.org/c/5QuaRfofXv

The HTTP Location header field is returned in responses from an HTTP server under two circumstances: 1. * To ask a web browser to load a different web page (URL redirection). In this circumstance, the Location header should be sent with an HTTP status code of 3xx. It is passed as part of the response by a web server when the requested URI has: 2. * Moved temporarily; 3. * Moved permanently; or 4. * Processed a request, e.g. a POSTed form, and is providing the result of that request at a different URI 5. * To provide information about the location of a newly created resource. In this circumstance, the Location header should be sent with an HTTP status code of 201 or 202.

AttributesValues
rdf:type
rdfs:label
  • HTTP location (en)
  • HTTP location (ru)
  • HTTP Location (zh)
rdfs:comment
  • HTTP-заголовок Location возвращается в ответах HTTP-сервера в двух случаях: 1. * Чтобы попросить браузер загрузить другую web-страницу (Перенаправление URL). В этом случае заголовок Location должен быть отправлен вместе с кодом состояния 3xx 2. * Для предоставления информации о новом местоположении ресурса. Код состояния должен быть 201 или 202 (ru)
  • HTTP Location 是在兩種情況下，因來自HTTP服務器的響應中返回頭域： 1. * 要求網頁瀏覽器加載其他網頁（網域名稱轉址）。在这种情况下，應該使用HTTP狀態碼3xx發送Location頭（Location header）。當請求的URI具有以下內容時，Web服務器響應傳遞： 2. * 临时移动; 3. * 永久移动； 4. * 處理請求，例如一個POST表單，以一個不同的URI来提供該請求的結果。 5. * 提供有關新創建資源位置的信息。在這種情況下，應該使用HTTP狀態碼201或202發送Location頭。 HTTP 1.1規範（IETF ）的過時版本需要完整的重定向URI。 IETF HTTP工作組發現，最受歡迎的Web瀏覽器允許傳遞相對URL（relative URL） 。因此，更新后的HTTP 1.1規範（IETF ）放寬了原始的約束，允許在位置標題中使用相對URL。 (zh)
  • The HTTP Location header field is returned in responses from an HTTP server under two circumstances: 1. * To ask a web browser to load a different web page (URL redirection). In this circumstance, the Location header should be sent with an HTTP status code of 3xx. It is passed as part of the response by a web server when the requested URI has: 2. * Moved temporarily; 3. * Moved permanently; or 4. * Processed a request, e.g. a POSTed form, and is providing the result of that request at a different URI 5. * To provide information about the location of a newly created resource. In this circumstance, the Location header should be sent with an HTTP status code of 201 or 202. (en)
dct:subject
Wikipage page ID
Wikipage revision ID
Link from a Wikipage to another Wikipage
Link from a Wikipage to an external page
sameAs
dbp:wikiPageUsesTemplate
has abstract
  • The HTTP Location header field is returned in responses from an HTTP server under two circumstances: 1. * To ask a web browser to load a different web page (URL redirection). In this circumstance, the Location header should be sent with an HTTP status code of 3xx. It is passed as part of the response by a web server when the requested URI has: 2. * Moved temporarily; 3. * Moved permanently; or 4. * Processed a request, e.g. a POSTed form, and is providing the result of that request at a different URI 5. * To provide information about the location of a newly created resource. In this circumstance, the Location header should be sent with an HTTP status code of 201 or 202. An obsolete version of the HTTP 1.1 specifications (IETF RFC 2616) required a complete absolute URI for redirection. The IETF HTTP working group found that the most popular web browsers tolerate the passing of a relative URL and, consequently, the updated HTTP 1.1 specifications (IETF RFC 7231) relaxed the original constraint, allowing the use of relative URLs in Location headers. (en)
  • HTTP-заголовок Location возвращается в ответах HTTP-сервера в двух случаях: 1. * Чтобы попросить браузер загрузить другую web-страницу (Перенаправление URL). В этом случае заголовок Location должен быть отправлен вместе с кодом состояния 3xx 2. * Для предоставления информации о новом местоположении ресурса. Код состояния должен быть 201 или 202 (ru)
  • HTTP Location 是在兩種情況下，因來自HTTP服務器的響應中返回頭域： 1. * 要求網頁瀏覽器加載其他網頁（網域名稱轉址）。在这种情况下，應該使用HTTP狀態碼3xx發送Location頭（Location header）。當請求的URI具有以下內容時，Web服務器響應傳遞： 2. * 临时移动; 3. * 永久移动； 4. * 處理請求，例如一個POST表單，以一個不同的URI来提供該請求的結果。 5. * 提供有關新創建資源位置的信息。在這種情況下，應該使用HTTP狀態碼201或202發送Location頭。 HTTP 1.1規範（IETF ）的過時版本需要完整的重定向URI。 IETF HTTP工作組發現，最受歡迎的Web瀏覽器允許傳遞相對URL（relative URL） 。因此，更新后的HTTP 1.1規範（IETF ）放寬了原始的約束，允許在位置標題中使用相對URL。 (zh)
prov:wasDerivedFrom
page length (characters) of wiki page
foaf:isPrimaryTopicOf
is Link from a Wikipage to another Wikipage of
is Wikipage disambiguates of
is foaf:primaryTopic of
Faceted Search & Find service v1.17_git147 as of Sep 06 2024


Alternative Linked Data Documents: ODE     Content Formats:   [cxml] [csv]     RDF   [text] [turtle] [ld+json] [rdf+json] [rdf+xml]     ODATA   [atom+xml] [odata+json]     Microdata   [microdata+json] [html]    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 08.03.3331 as of Sep 2 2024, on Linux (x86_64-generic-linux-glibc212), Single-Server Edition (378 GB total memory, 83 GB memory in use)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2024 OpenLink Software