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.

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

Can {searchTerms} Use Spaces Instead of +? #68

Open
Foreeps opened this issue Jan 16, 2025 · 2 comments
Open

Can {searchTerms} Use Spaces Instead of +? #68

Foreeps opened this issue Jan 16, 2025 · 2 comments

Comments

@Foreeps
Copy link

Foreeps commented Jan 16, 2025

Hello,

I've run into a search engine that treats "two+words" as a single term. While all the rest I've seen are happy with '+' deliminating the terms the way {searchTerms} does it normally, is there a way to modify it to use spaces instead, or an alternative {spaceTerms} parameter or something?

Thank you!

@dewitt
Copy link
Owner

dewitt commented Jan 16, 2025

It's in interesting question, and I can't recall whether the use of '+' has been discussed before. The only thing the spec says is that "The value must be URL-encoded." As such, perhaps try %20 for that search engine and see what happens?

@Foreeps
Copy link
Author

Foreeps commented Jan 16, 2025

That's what I was asking - how can I get {searchTerms} to use spaces, %20, instead of +?

Or do you mean typing "%20" in my search instead of spaces? That isn't a very user-friendly solution, and it doesn't actually work: a search for "two%20words" literally searches for that, converting it in the address bar to "test%2520words".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants