Repository navigation
Fetch: Cross-Origin Requests #495
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
diogoosz
wants to merge
1
commit into
javascript-tutorial:master
Choose a base branch
from
diogoosz:translate-fetch-crossorigin
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
10 changes: 5 additions & 5 deletions
10
5-network/05-fetch-crossorigin/1-do-we-need-origin/solution.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,9 +1,9 @@ | ||
| We need `Origin`, because sometimes `Referer` is absent. For instance, when we `fetch` HTTP-page from HTTPS (access less secure from more secure), then there's no `Referer`. | ||
| Precisamos de `Origin`, porque às vezes `Referer` está ausente. Por exemplo, quando fazemos `fetch` de uma página HTTP a partir de HTTPS (acessar algo menos seguro a partir de algo mais seguro), então não há `Referer`. | ||
|
|
||
| The [Content Security Policy](http://en.wikipedia.org/wiki/Content_Security_Policy) may forbid sending a `Referer`. | ||
| A [Content Security Policy](http://en.wikipedia.org/wiki/Content_Security_Policy) pode proibir o envio de um `Referer`. | ||
|
|
||
| As we'll see, `fetch` has options that prevent sending the `Referer` and even allow to change it (within the same site). | ||
| Como vamos ver, `fetch` tem opções que impedem o envio do `Referer` e até permitem alterá-lo (dentro do mesmo site). | ||
|
|
||
| By specification, `Referer` is an optional HTTP-header. | ||
| Pela especificação, `Referer` é um cabeçalho HTTP opcional. | ||
|
|
||
| Exactly because `Referer` is unreliable, `Origin` was invented. The browser guarantees correct `Origin` for cross-origin requests. | ||
| Exatamente porque `Referer` não é confiável, `Origin` foi inventado. O navegador garante um `Origin` correto para requisições cross-origin. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A segunda pergunta mudou de sentido. O original ("Is it possible that there is no
RefererorOrigin, or is it incorrect?") pergunta se os cabeçalhos podem estar ausentes ou conter um valor errado. Já "ou isso está incorreto?" dá a entender "ou essa afirmação está incorreta?", o que não corresponde ao que a solução responde. Que tal assim?