Updated for protection against MIME & XSS based attacks #450
Conversation
This file contains 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
|
@yashdusing can you use the methods listed in #459 to verify the changes you made for HTTP Headers works and mention the results here. |
|
It shows up as unprotected (the same as shown in #459). Although I do have a doubt. 0.0.0.0:8000 is the home page site which has no headers on it. The headers are added to the ajax calls made to import/export or other apps so isn’t it supposed to show up not protected ?(unless we somehow added XSS protection to home page) |
|
So 0.0.0.0:8000/layer_parameter also is shown as unprotected 😓. I will have to figure out why |
yashdusing
force-pushed
the
attacks_protection
branch
from
5117147
to
9ec3aeb
Compare
|
|
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.
Updated headers to ajax call for protection against MIME and XSS based attacks