숫자 태그의 기존 URL에서 500 오류 발생 (Google 크롤 실패)

[Ed_S]

My forum has a tag which happens to be a 4 digit number, 6309. It’s been around for a while. It displays OK on posts, and the URL in that case is /tag/210-tag/210

But rather than a pretty 404 page, a url like /tag/6309 is returning a server error:

Oops

The software powering this discussion forum encountered an unexpected problem. We apologize for the inconvenience.

I’m guessing that some time previously that was a valid way to refer to the tag. Because it’s a server error, google’s crawler is complaining to me about it.

Tag page looks like this:

I think 404 would be correct.

[supermathie (Michael Brown)]

Yeah, that’s not pretty:

ActionView::Template::Error (No route matches {action: "tag_feed", controller: "tags", tag_id: "9999"})
  app/views/list/list.erb:136
  app/views/list/list.erb:134
  lib/topic_list_responder.rb:16:in 'block (2 levels) in TopicListResponder#respond_with_list'
  lib/topic_list_responder.rb:7:in 'TopicListResponder#respond_with_list'
  app/controllers/tags_controller.rb:223:in 'block (2 levels) in <class:TagsController>'
  app/controllers/tags_controller.rb:229:in 'TagsController#show'
  app/controllers/application_controller.rb:447:in 'block in ApplicationController#with_resolved_locale'
  app/controllers/application_controller.rb:447:in 'ApplicationController#with_resolved_locale'
  app/controllers/application_controller.rb:1098:in 'ApplicationController#ensure_dont_cache_page'
  lib/middleware/omniauth_bypass_middleware.rb:35:in 'Middleware::OmniauthBypassMiddleware#call'
  …

We should fix that error; we also might be able to fallback to looking for an all-numeric tag name if the tag id isn’t found.

@Ed_S

I’m guessing that some time previously that was a valid way to refer to the tag.

Wayback first noticed that tag appearing on 2025-05-13 and its url was https://retrocomputingforum.com/tag/6309 which worked at the time and up until 2025-12-16.

[Ed_S]

Ah, well-spotted. Perhaps some sort of 3xx redirection response would be right, even better than 404, in case the tag is valid?

[Ed_S]

(I’m not sure if this should be in the UX or Bug category.)

[nat (Natalie T)]

All good. We have eyes on this issue and will be issuing a fix.

Tag name resolution at /tag/name should and must remain compatible, this is an explicit choice and decision we’ve made. But I think in this case it’s a number so perhaps the name resolution must have gone wrong at the backend.

[pmusaraj (Penar Musaraj)]

Thanks for the report, this should fix the issue once merged:

https://github.com/discourse/discourse/pull/39113