Only one X-Served-By with shielding
According to https://docs.fastly.com/guides/performance-tuning/understanding-cache-hit-and-miss-headers-with-shielded-services# the X-Served-By header should contain two nodes if shielding is enabled. Except when the request happens to go directly to the shielding datacenter.
Still, we see a lot of
and the like while Frankfurt is selected as shield.
Any idea how this could happen?
We have quite a complicated VCL (>400 lines).
Thanks for ideas!
There are things that can be set in the UI that will bypass shielding, so there may be problems there. It's hard to tell without looking at your service directly. If you'd like, send us an email at email@example.com and we'll take a look.
Please sign in to leave a comment.