chore: enable js-profiling Document Policy#219
Conversation
|
@codex could you review this PR please? |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8b68162437
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 644706b3f3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ], | ||
| }, | ||
| corsBehavior: { | ||
| accessControlAllowCredentials: true, |
There was a problem hiding this comment.
Avoid wildcard origin when allowing credentials
This CORS policy enables accessControlAllowCredentials: true while also allowing origin *, which produces an invalid credentialed CORS response (Access-Control-Allow-Origin: * with credentials) and causes browsers to reject cross-origin requests that include cookies or auth credentials. In environments where the frontend is fetched cross-origin with credentials, those requests will fail despite this policy intending to improve telemetry/correlation behavior.
Useful? React with 👍 / 👎.
No description provided.