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

Relative paths for search engines #45

Open
ghost opened this issue Jan 6, 2023 · 0 comments
Open

Relative paths for search engines #45

ghost opened this issue Jan 6, 2023 · 0 comments

Comments

@ghost
Copy link

ghost commented Jan 6, 2023

The problem

For most use-cases, absolute paths are fine as a website is mostly only hosted on one domain.

However, when it comes to software that is made to be deployed to many different domains, it requires the opensearch file to be edited for each instance of the deployed software (see piped and libreddit having issues with this.

Tried solutions

Even when editing the opensearch file, it can cause issues if that one server can be accessed from multiple domains, for example if it has an onion site on tor.

Another workaround that could actually work would be to edit the file and insert the domain using the Host http header, but that adds a level of complexity that shouldn't be necessary.

Ideal solution

What I request is that the opensearch standard allow for relative paths to be used for search engines, allowing for the browser to use the current host in the url.

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

0 participants