You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: