-
Notifications
You must be signed in to change notification settings - Fork 76
Adds a no-cache header to slack error responses #944
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
Conversation
🦋 Changeset detectedLatest commit: db10980 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
commit: |
}); | ||
return new Response(JSON.stringify(completions), { | ||
headers: { | ||
'Content-Type': 'application/json', |
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.
removed caching from here, let gitbook handle caching
status: error instanceof ExposableError ? error.code : 500, | ||
headers: { | ||
'Content-Type': 'application/json', | ||
'Cache-Control': 'no-cache, no-store', |
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.
Error responses shouldn't be cached.
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.
The idea is to fix the logic in gitbook, not to cache error responses, but I want to validate that this works regardless.
Fixed in gitbook |
Made the wrong fix #935. The error response is what gets cached first due to the lack of authentication permissions.
I want to test if this works as expected before I make any changes to gitbook-x