400 Bad Request since 5.2.1

[sacr3dc0w]

Expected behavior

stencil start boots up and localhost loads.

Actual behavior

400 Bad Request
Request Header Or Cookie Too Large
cloudflare

Steps to reproduce behavior

Install 5.2.2, run stencil start

Environment

Stencil-cli version stencil --version: 5.2.2

Node version node -v: v14.20.0

NPM version npm -v: 6.14.17

OS: MacOS Monterey 12.6

[sacr3dc0w]

Back from traveling. I’ve done more digging around.

• We have five online stores, only one is impacted.
• Encountering the issue in 5.2.1.
• Downgrading to 5.2.0 resolves the problem for now.

[sacr3dc0w]

This is still occurring in 5.2.4. This happens with our custom theme and with the base cornerstone theme. Is our store to remain on 5.2.0 to circumvent whatever issue is occurring? While fine for the short term, that doesn't seem like a long-term fix.

Our development team would very much like to enjoy redirects stalling out locally bug fix #1000 that's in 5.2.4

Appreciate any guidance toward resolving the original issue.

[sacr3dc0w]

When I empty the category, page, and product objects in the customLayouts object for mapping custom layouts in our config.stencil.json file, the cloudflare error goes away. However, we are unable to add products to the cart locally.

config.stencil.json.zip

[sacr3dc0w]

#1019 resolved this issue - Thank you for that! It appears it introduced a new one where the URL mapped to a custom template uses the page_type template instead of the custom template it's been mapped with. Meaning custom product templates revert to the main product.html template, custom page templates revert to the main page.html template, etc, so I'll be posting the details of that in a separate thread.