Observed behavior:
Setting the language domain prefixes the path with the domain, as if it were using path prefixes to determine languages. For example, setting the language domain for English to "en.dev.wikibiblio.org" makes links like "en.dev.wikibiblio.org/node/add". These links fail.

Expected behavior:
No change to paths. A domain match sets the locale.

Comments

gábor hojtsy’s picture

The description of the domain field:

Optional custom domain with protocol (eg. "http://example.de" or "http://de.example.com" for the German version). This value is only used in the "Domain" negotiation mode. If left empty and in "Domain" mode, this language will not be accessible.

Indeed, if you don't provide a protocol identifier, it will look like as if it is erroneously included in the path. This might use a validation to look for a protocol, and alert the admin if there was no protocol provided. If you provide a domain however, the domain is not only used in domain negotiation, but also when printing links to content in specific languages. This latter fact is not described here unfortunately, so we might need a documentation update.

gábor hojtsy’s picture

Priority: Critical » Normal

Not critical.

david strauss’s picture

Why is the protocol required? That will cause issues with sites that need HTTP and HTTPS support.

gábor hojtsy’s picture

Otherwise we cannot offer you a possibility to ask for a protocol or a port to be used.

chx’s picture

Status: Active » Closed (works as designed)