-
Notifications
You must be signed in to change notification settings - Fork 10
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
[API Docs] update latest API docs #829
Conversation
This pull request is automatically being deployed by Amplify Hosting (learn more). |
1c50617
to
556e57c
Compare
0f31c40
to
c83200b
Compare
d1ec89a
to
57d504f
Compare
da8b6c6
to
4de0330
Compare
4de0330
to
d701dce
Compare
@@ -576,7 +576,7 @@ <h4 id="mesh_object_declarative_import">meshObject Declarative Import</h4> | |||
Vary: Access-Control-Request-Headers | |||
Content-Type: application/vnd.meshcloud.api.meshobjects.v1+json | |||
X-Content-Type-Options: nosniff | |||
X-XSS-Protection: 1; mode=block | |||
X-XSS-Protection: 0 |
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.
@sttomm can you review that whether this is related to library upgrades
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.
yes, it is related to upgrading to Spring Boot 3.0 (and especialyl Spring Security 6). Setting this header to 0 is the new recommendation by OWASP. So I think this change is a good one. It seems like the old default did more harm than good in the end. So it should be good, that it is set to 0 now. spring-projects/spring-security#9631
14245c8
to
ac018a6
Compare
ac018a6
to
9f6db2f
Compare
The latest API docs from meshStack builds on the develop branch.