#3256 docs.fedoraproject.org inaccessible for Chinese (Taiwan) users
Closed: Fixed None Opened 10 years ago by wwycheuk.

= bug description =
http://docs.fedoraproject.org is inaccessible when user browser's 'accepting-language' is set to 'Chinese (Taiwan)' (zh_TW)
= bug analysis =

= fix recommendation =

This seems to be a problem with the docs content, not the config of the webserver.

Can you file a bug against Fedora Docs or bring it to the docs group's attention?


Someone in the docs team said this is not their problem. What should I do?

Who was that? Where did they say it?

Did they say where the issue should be addressed?

When you say "inaccessable" what do you mean?

The page never loads?

The page loads but is in en_US?

The page loads but is blank?

From testing here, I seem to always get the en_US page... which may be because there are no translations for it.

The issue Walter was seeing was that the page would appear largely blank (with the exception of the Fedora Documentation header) and constantly refreshing / not displaying the doc site. I was able to reproduce this by setting my preferred language in Firefox to zh-TW.

What was happening is that when you hit [http://docs.fedoraproject.org] your preferred locale is evaluated and you are redirected to the welcome page for it, in this case [http://docs.fedoraproject.org/zh-TW/index.html]. No welcome page existed in the zh-TW directory so the site's 404 handling kicked in, redirecting to [http://docs.fedoraproject.org]. At this point of course the locale selection logic kicked in again, putting the user's browser in an infinite loop.

A zh-TW translation of the welcome page did exist in Transifex and I have now pulled into the docsite-publican.git and pushed to the live site. I believe this should resolve this issue. The thread where Walter assisted me with working this out is recorded here:


Great. So everything is fixed now?

Thanks very much for tracking this down...

Yes, I haven't received confirmation from Walter yet but from my end it now looks to be fixed.

The problem is fixed now. Thank you both very much.

Login to comment on this ticket.