Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

FR: Support for URIs larger than 255 chars #539

Closed
joepagan opened this issue Jul 18, 2023 · 4 comments
Closed

FR: Support for URIs larger than 255 chars #539

joepagan opened this issue Jul 18, 2023 · 4 comments
Labels
enhancement New feature or request

Comments

@joepagan
Copy link

joepagan commented Jul 18, 2023 •
edited

Was debugging why some search results uris on a site we manage were bypassing cache, and unfortunately got the log:

Page not cached because it exceeds the max URI length of 255 characters. [https:/...

It looks like this is by design on an older github issue because craft3 supposed mysql5.5+

However craft4 supports mysql5.7.8+

Can we please get support for this for blitz v4 and onwards?
@joepagan joepagan added the enhancement New feature or request label Jul 18, 2023
@joepagan joepagan changed the title Support for URIs larger than 255 chars? FR: Support for URIs larger than 255 chars Jul 18, 2023
@bencroker
Copy link
Collaborator

bencroker commented Jul 18, 2023 •
edited

Yes, I’ll look into making this happen. What version of Blitz is the site currently running?

@joepagan
Copy link
Author

Amazing thanks Ben! Currently running 4.2.3

@bencroker
Copy link
Collaborator

bencroker commented Jul 19, 2023 •
edited

Added this as a config setting in 4fb3ec2 for the upcoming 4.5.0 release. Be sure to read the caveats before changing.

@bencroker
Copy link
Collaborator

Released in version 4.5.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@joepagan @bencroker