Hey guys,
Our dev site here. dev.styxmill.com isn’t being proxied. I can’t work out why. Other sub domains and the main domain are proxied correctly.
Dev was changed to proxy about a week ago so it can’t be a propagation issue. I tried deleting the A record and adding it again.
Any ideas?
Thanks in advance.
Antony
What makes you think it it isn’t proxied properly?
I’m checking the response headers for cf-ray and cf-cache-status. Here’s the response headers for
dev site
cache-control: no-store, no-cache, must-revalidate
cache-control: public
content-encoding: br
content-length: 11852
content-type: text/html; charset=UTF-8
date: Wed, 10 May 2023 01:19:27 GMT
expires: Thu, 19 Nov 1981 08:52:00 GMT
pragma: no-cache
referrer-policy: no-referrer
server: Apache
strict-transport-security: max-age=10886400;
vary: Accept-Encoding
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN, SAMEORIGIN
x-frame-options: SAMEORIGIN
x-permitted-cross-domain-policies: none
x-xss-protection: 1; mode=block
I can see them in the main site
alt-svc: h3=“:443”; ma=86400, h3-29=“:443”; ma=86400
cf-cache-status: DYNAMIC
cf-ray: 7c4e5c2b7960a87c-SYD
content-encoding: br
content-type: text/html; charset=UTF-8
date: Wed, 10 May 2023 01:20:30 GMT
server: Cloudflare
vary: Accept-Encoding
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
@developers31 It looks to me you’re seeing a cached version of the page. I’m not able to replicate that at all.
Ok thanks guys. It must be DNS cache from my side.
