Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Fetch: Cross-Origin Requests#427

New issue

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

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

Already on GitHub?Sign in to your account

Merged
Merged
Show file tree
Hide file tree
Changes fromall commits
Commits
Show all changes
23 commits
Select commitHold shift + click to select a range
e396038
se actualiza con la version en ingles
MaskeZenOct 6, 2020
ca6607b
traduccion parcial
MaskeZenOct 16, 2020
70ecc20
corss-origin-request articulo completo
MaskeZenOct 19, 2020
ac12441
se agrega task y solution
MaskeZenOct 21, 2020
576213a
Merge branch 'master' into cross-origin-requests
joaquinelioOct 22, 2020
538975a
Update 5-network/05-fetch-crossorigin/article.md
MaskeZenOct 23, 2020
f134240
Update 5-network/05-fetch-crossorigin/1-do-we-need-origin/solution.md
MaskeZenOct 23, 2020
15fe5de
Update 5-network/05-fetch-crossorigin/article.md
MaskeZenOct 23, 2020
769cf76
Update 5-network/05-fetch-crossorigin/article.md
MaskeZenOct 23, 2020
86fa874
Update 5-network/05-fetch-crossorigin/article.md
MaskeZenOct 23, 2020
6cbb169
Update 5-network/05-fetch-crossorigin/article.md
MaskeZenOct 23, 2020
cc63b61
Update 5-network/05-fetch-crossorigin/article.md
MaskeZenOct 23, 2020
5547fd8
Update 5-network/05-fetch-crossorigin/article.md
MaskeZenOct 23, 2020
14f1e35
Update 5-network/05-fetch-crossorigin/article.md
MaskeZenOct 23, 2020
11060b4
Update 5-network/05-fetch-crossorigin/article.md
MaskeZenOct 23, 2020
d2a3367
Update 5-network/05-fetch-crossorigin/article.md
MaskeZenOct 23, 2020
3bdb479
Update 5-network/05-fetch-crossorigin/article.md
MaskeZenOct 23, 2020
503f717
Update 5-network/05-fetch-crossorigin/article.md
MaskeZenOct 23, 2020
939b5ae
Update 5-network/05-fetch-crossorigin/article.md
MaskeZenOct 23, 2020
a12276f
Update 5-network/05-fetch-crossorigin/article.md
MaskeZenOct 23, 2020
3114ca5
Update Cross-Origin Request #427
MaskeZenOct 27, 2020
2d4d85f
update cross-origin-request
MaskeZenOct 27, 2020
106425e
update cross-origin-request
MaskeZenOct 27, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
View file
Open in desktop
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
We need`Origin`,because sometimes`Referer`is absent. For instance, when we`fetch` HTTP-page fromHTTPS (access less secure from more secure),then there's no `Referer`.
Necesitamos la cabecera`Origin`,ya que en algunos casos`Referer`no está presente. Por ejemplo, cuando realizamos un`fetch`a una páginaHTTP desde unaHTTPS (acceder a un sitio menos seguro desde uno más seguro),en ese caso no tendremos el campo `Referer`.

The [Content Security Policy](http://en.wikipedia.org/wiki/Content_Security_Policy)may forbid sending a `Referer`.
La [Política de seguridad de contenido](http://en.wikipedia.org/wiki/Content_Security_Policy)puede prohibir el envío de `Referer`.

As we'll see, `fetch`has options that prevent sending the`Referer`and even allow to change it (within the same site).
Como veremos, `fetch`tiene opciones con las que es posible evitar el envío de`Referer`e incluso permite su modificación (dentro del mismo sitio).

By specification, `Referer`is an optional HTTP-header.
Por especificación, `Referer`es una cabecera HTTP opcional.

Exactly because`Referer`is unreliable,`Origin`was invented. The browser guarantees correct`Origin`for cross-origin requests.
Por el hecho de que`Referer`no es confiable, la cabecera`Origin`ha sido creada. El navegador garantiza el envío correcto de`Origin`para las solicitudes de origen cruzado.
16 changes: 8 additions & 8 deletions5-network/05-fetch-crossorigin/1-do-we-need-origin/task.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -2,11 +2,11 @@ importance: 5

---

#Why do we needOrigin?
#¿Por que necesitamos el origen (Origin)?

As you probably know, there'sHTTP-header `Referer`,that usually contains an url of the page which initiated a network request.
Como seguramente ya sepas, existe la cabeceraHTTP `Referer`,la cual por lo general contiene la url del sitio que generó la solicitud.

For instance, when fetching`http://google.com`from `http://javascript.info/some/url`,the headers look like this:
Por ejemplo, cuando solicitamos la url`http://google.com`desde `http://javascript.info/alguna/url`,las cabeceras se ven de este modo:

```
Accept: */*
Expand All@@ -16,13 +16,13 @@ Connection: keep-alive
Host: google.com
*!*
Origin: http://javascript.info
Referer: http://javascript.info/some/url
Referer: http://javascript.info/alguna/url
*/!*
```

As you can see, both `Referer`and `Origin`are present.
Tal como se puede ver, tanto `Referer`como `Origin`están presentes.

The questions:
Las preguntas:

1.Why`Origin`is needed, if `Referer`has even more information?
2.Is it possible that there's no `Referer`or `Origin`,or is it incorrect?
1.¿Por qué la cabecera`Origin`es necesaria, si `Referer`contiene incluso más información?
2.¿Es posible que no se incluya `Referer`u `Origin`,o que contengan datos incorrectos?
Loading
[8]ページ先頭
©2009-2025 Movatter.jp