1C:Enterprise platform - English (it set as default, but as far as there is no Spanish support it shows in english) Configuration - Spanish, English Thin client (default setting). Normally it will open with Eng platform interface and Spanish configuration. PostgreSQL es_EC collation
we are not talking about Spanish support here. We are talking that there is no way you could use 1C Ent applications on like 20% of world computers because it have a bug since version 8.3.10. Previous versions work fine. Imagine that we still suggest to our clients use 8.3.6 version, because of numerous bugs of the latest versions. It is just unpredictable what to expect.
We can take a look at your client's environment. Though, it can only give us a confirmation you have an issue that can be reproduced in this environment with this particular configuration, which you probably will not share with us.
What we actually need is a simple sample configuration that you can share with us. We know your environment, we can simulate it. So, with a sample configuration in this environment we will be able reproduce the issue and then pass it to our dev team to fix it.
Vladimir, it is important that you connect via http (but still using thin client). If you use tcp connection everything works fine. You should use default apache distr (2.4) to reproduce the issue. p.s. no SSL, TLS encryption was used
We could reproduce the issue with a simple infobase published to Apache 2.4.6 on a Linux-running server and a connection to the infobase from a Windows-running machine by using 1C:Enterpise's thin client via http protocol.
We informed our dev team about the issue. They are investigating it.
Thank you for notifying us about the issue. And for your patience
Please inform dev. team that this issue is super important to us and I think to many international clients, because it prohibits use of latest version of platform for us. The issue is reproduced from 8.3.10 up to 8.3.12
After your report, our dev team found out the root cause of the issue. They already fixed the issue in test versions of 1C:Enterprise platform 8.3.13 and we expect to get it fixed in 8.3.12 as well.
The root cause is that sometimes the Apache web server returns the following string in response headers: Content-Language: en-us-posix
1C:Enterprise platform tries to place this string as the locale name to the database cache, but the string does not fit to the container for the locale name. As a result, the application raises an error and then fails.
So far, you can use the following workaround for the issue:
Explicitly specify the value of the Content-Language property in the Apache configuration for the published infobase. To set the property value, you can use any language tag defined in the HTTP standard. For instance, "en", "es", "ru", "en-US", "es-EC".
# 1c publication
Alias "/testapp" "/var/www/html/testapp/"
Header set Content-Language "es-EC" # Add such a string and restart Apache
Allow from all