Page doesn't exist or is private different font and different language

Contribute UX

AI-generated summary

Page doesn’t exist or is private in different font and language

ondrej reported that the “Page doesn’t exist or is private” message appeared in a different font and Russian language on their screen. simon explained that this might be due to the set locale from accept language header setting, which sets the locale for anonymous users based on their browser’s language headers. simon suggested that ondrej check their browser’s language settings.

After checking, ondrej found that the issue was no longer present. simon speculated that there might have been a caching issue related to the set locale from accept language header setting, which could have caused the 404 page to be displayed with the incorrect locale. Recent changes to Discourse’s caching mechanism should prevent this issue, but simon asked ondrej to report if the issue occurs again.

1

Hello all :waving_hand:

Why is my ‘page doesn’t exist or is private’ in a different font and written in what seems to be Russian?

Screenshot_20200903-131853
Screenshot_20200903-1318531080×1920 186 KB

2 Likes
2

It seems that the not-found page treats users as anonymous users. We have the set locale from accept language header setting enabled on Meta. This setting is intended to set the locale for anonymous users to the locale that’s sent with their browser’s language headers.

When I set my browser’s locale to French, the not-found page uses the French locale even if I’m logged into Meta. This might be acceptable, but if a locale that is not set in your browser’s language settings is being displayed for you, it is a problem.

Are you able to check your browser’s language settings? On Chrome, the language is set in the Advanced settings:

image
image775×364 10.8 KB

3 Likes
3

Hi Simon,

I’ll take a look in a while. Thanks for your reply. :smiley:

1 Like
4

Hi

Screenshot_20200904-124215
Screenshot_20200904-1242151080×1920 78.8 KB

I checked today and I found it like this. Not sure what happened yesterday at all.

1 Like
5

Thanks for checking that. My concern is that there could be a caching issue related to the set locale from accept language header setting that would cause the 404 page to be displayed with the incorrect locale under some circumstances. It seems likely that is what happened the previous time that you accessed that page.

There were some recent changes made to how Discourse caches pages for anonymous users. Those changes should prevent this from happening, but it’s possible that there are still issues with caching the 404 page.

2 Likes
6

I see. Thanks for the detailed clarification. If I see it again I will let you know.