-
Notifications
You must be signed in to change notification settings - Fork 94
enable origin shield for docs.rs webserver #711
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
This comment was marked as outdated.
This comment was marked as outdated.
ddc1e6e to
cd8ae65
Compare
113bbc5 to
58a07d6
Compare
|
note: let's try to test this first somehow |
|
I tried to apply this but it's not compatible with wasm services. I asked clarification to fastly's support |
0b5ee4e to
127cf0d
Compare
|
@marcoieni I updated the compute logic to what I think would the a correct approach. Right now the code is written very defensively, I want to see some logs when we play around with it. What do you think? Also about the logic? |
127cf0d to
0ea4907
Compare
marcoieni
left a comment
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.
this makes sense to me. Let me know when you want to apply it 👍
|
applied |
This PR would enable fastly origin shield for our webserver.
We have a huge number of pages that are accesed regularly, but not that often. Right now every POP manages its own cache, and also requests the origin on its own.
I hope this feature can help to improve cache ratio and offload more cachable requests from our server.
see also: