#259 Wildcard Serving

Open
opened 2 weeks ago by n · 4 comments
n commented 2 weeks ago

As discussed in #227, wildcard serving is hurting search results for Codeberg.
I propose returning a 404 error or redirecting to codeberg.org/*.

As discussed in #227, wildcard serving is hurting search results for Codeberg. I propose returning a 404 error or redirecting to `codeberg.org/*`.
hw commented 1 week ago
Owner

We need a proper technical solution here: redirects do not work as browsers reject them with certificate error. Any idea?

We need a proper technical solution here: redirects do not work as browsers reject them with certificate error. Any idea?
lhinderberger commented 1 week ago
Collaborator

@hw - While a redirect wouldn’t work for browsers, it would work for crawlers, preventing duplicate search results. But in general, returning 404 Not Found would be the cleaner solution, as redirecting suggests the URL is valid.

@hw - While a redirect wouldn't work for browsers, it would work for crawlers, preventing duplicate search results. But in general, returning `404 Not Found` would be the cleaner solution, as redirecting suggests the URL is valid.
hw commented 1 week ago
Owner

crawlers are redirected to TLS too, and then fail the cert check just like a browser?

crawlers are redirected to TLS too, and then fail the cert check just like a browser?
lhinderberger commented 1 week ago
Collaborator

The search results from the other issue suggested differently, if I remember correctly. But either way, I think a 404 would be the better option 😉

The search results from the other issue suggested differently, if I remember correctly. But either way, I think a 404 would be the better option :wink:
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.