routing: SECURED flag warning #455
Merged
Conversation
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
| @@ -299,6 +299,8 @@ HTTPS | |||
|
|
|||
| U routy lze vynutit používání zabezpečeného protokolu HTTPS uvedením příznaku `SECURED`. Vhodné je to například pro administraci nebo pro přihlašování uživatelů. HTTPS musí podporovat váš hosting. | |||
|
|
|||
| Příznak neslouží jako bezpečnostní opatření blokující HTTP. Užívá se pouze pro kanonizaci url! | |||
There was a problem hiding this comment.
- "nezabezpečené spojení přes HTTP"
- "generování a kanonizaci"
There was a problem hiding this comment.
Příznak neslouží jako bezpečnostní opatření zabraňující přístup přes HTTP. Ovlivňuje pouze podobu generovaných adres a k přesměrování dochází díky kanonizaci URL v presenteru.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
https://forum.nette.org/cs/26348-route-secured-nevynucuje-https-100