WiseGuru
CDCloudflare Developers
•Created by WiseGuru on 11/15/2023 in #pages-help
11ty HTTP Header Hardening
That fixed it; I had previously made the passthrough to the eleventy.js, but I didn't give the full path to the headers file. I still need to tweak the headers to do what I want, but the main issue is resolved. Thank you!
10 replies
CDCloudflare Developers
•Created by WiseGuru on 11/15/2023 in #pages-help
11ty HTTP Header Hardening
I just found this guide on adding _headers files to Eleventy sites built on Cloudflare, and I'm going to give it a try. https://jonkuperman.com/custom-headers-eleventy-cloudflare-pages/
10 replies
CDCloudflare Developers
•Created by WiseGuru on 11/15/2023 in #pages-help
11ty HTTP Header Hardening
Ok, thanks; when I check there, I only see example headers (as opposed to "Assets Uploaded" which shows a list. Where do I need to put the _headers file in my GitHub repo so it gets added to the output folder on build?
10 replies
CDCloudflare Developers
•Created by WiseGuru on 11/15/2023 in #pages-help
11ty HTTP Header Hardening
I'm still running into issues with the local deployment that are unrelated to the headers issue; it looks like a version dependency issue between Sharp and Node.js, and I've tried a couple versions (including 18.17.1, which is what Cloudflare appears to use), but no luck. If we can just use Cloudflare information, as the modules seem pretty picky, that would be great.
10 replies
CDCloudflare Developers
•Created by WiseGuru on 11/15/2023 in #pages-help
11ty HTTP Header Hardening
I'm having trouble with that; for some reason, the build is failing locally when it's fine on Cloudflare. I'm troubleshooting the error, but in the meantime, is there a way to check the output directory on Cloudflare?
10 replies
CDCloudflare Developers
•Created by WiseGuru on 11/15/2023 in #pages-help
11ty HTTP Header Hardening
I'm sorry, I'm not sure where to check that, or where to run things like "npm audit fix"
10 replies
CDCloudflare Developers
•Created by WiseGuru on 11/10/2023 in #pages-help
Upgraded to Pro, but new builds are still failing
Yes, it was a mistake on my end, not Cloudflare; one of my page's name was changed (from "Pages" to "pages") and the build process I was using didn't know how to deal with it. I deleted the offending version and ran the deployment again, and it's now fine.
4 replies
CDCloudflare Developers
•Created by WiseGuru on 11/10/2023 in #pages-help
Upgraded to Pro, but new builds are still failing
Actually, it might be my mistake; verifying, will follow up shortly either with errors or confirmation of resolution.
4 replies