Closed thescientist13 closed 6 months ago
Doh, forgot that cURL doesn't follow redirects, so have to pass the -L
flag. Now it is showing the correct results 💯
✗ curl -IL https://www.blissfestri.com/
HTTP/2 301
content-type: text/plain; charset=utf-8
date: Thu, 02 May 2024 17:19:40 GMT
location: https://blissfestri.com/
server: Netlify
strict-transport-security: max-age=31536000
x-nf-request-id: 01HWX5399XV69SZM62NMNZA8TN
HTTP/2 301
age: 0
cache-control: public,max-age=0,must-revalidate
cache-status: "Netlify Edge"; fwd=miss
content-type: text/plain; charset=utf-8
date: Thu, 02 May 2024 17:19:40 GMT
location: https://www.blissri.com/
server: Netlify
strict-transport-security: max-age=31536000
x-nf-request-id: 01HWX539DFGMYR8XYZ1EHC4T91
content-length: 39
HTTP/2 301
content-type: text/plain; charset=utf-8
date: Thu, 02 May 2024 17:19:40 GMT
location: https://blissri.com/
server: Netlify
strict-transport-security: max-age=31536000
x-nf-request-id: 01HWX539HKMG889SSB1GVJM4WV
HTTP/2 200
accept-ranges: bytes
age: 0
cache-control: public,max-age=0,must-revalidate
cache-status: "Netlify Edge"; fwd=miss
content-type: text/html; charset=UTF-8
date: Thu, 02 May 2024 17:19:40 GMT
etag: "2c68be539d57848d4a45b06093dde40a-ssl"
server: Netlify
strict-transport-security: max-age=31536000
x-nf-request-id: 01HWX539N46BVVM7P3Z8WYSHNP
content-length: 24032
Summary
After instrumenting https://github.com/AnalogStudiosRI/www.blissfestri.com/pull/139 as part of #1 , I can confirm browsers are correctly redirecting from
www.blissfestri.com
->www.blissri.com
But
cURL
is showing something different?Details
If it's working for browsers, then I suppose its not a Netlify issue, but strange that
cURL
would be the one not handling it correctly?Either way, while its good browsers are picking it up, would be good to know why this is happening so as not to avoid any possible issues with SEO or searches as we get closer to the day of the festival.