Skip to content

Conversation

reakaleek
Copy link
Member

GET requests are cached on the edge. which means, once a user with VPN gets a 200 OK, all users in the region get a 200 OK, which is not the intended behaviour

POST requests are not cached

GET requests are cached on the edge. which means, once a user with VPN gets a 200 OK, all users in the region get a 200 OK, which is not the intended behaviour

POST requests are not cached
@reakaleek reakaleek requested a review from a team as a code owner September 8, 2025 13:23
@reakaleek reakaleek requested a review from cotti September 8, 2025 13:23
@reakaleek reakaleek self-assigned this Sep 8, 2025
@reakaleek reakaleek added the fix label Sep 8, 2025
Copy link
Member

@Mpdreamz Mpdreamz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why POST and not just the GET (while we investigate the HEAD issue on fastly?)

@reakaleek
Copy link
Member Author

Why POST and not just the GET (while we investigate the HEAD issue on fastly?)

POST requests are not cached on the edge.
GET requests are. Which results in 200 for other users once the someone logs in VPN and opens it.

@reakaleek reakaleek merged commit 11912ee into main Sep 8, 2025
19 of 20 checks passed
@reakaleek reakaleek deleted the feature/fix-root-api-check branch September 8, 2025 15:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants