You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an IDN domain (with an umlaut) as host in my ejabberd config. Certificates are issued for the domain in punycode. File upload via mod_http_upload from Conversations 2.9.6 to the internal fileserver would fail with standard configuration, so here is what I tried:
Working
1
host: punycode
put_url: @host@
comment: Works, but nobody wants JIDs in punycode.
In the failing cases, ejabberd logs that it cannot handle a put request to the host (written in punycode). From the discussion in the Conversations MUC i assume that while Conversations sends http headers (correctly) with punycode, ejabberd should transform them to unicode when interpreting them as host.
The text was updated successfully, but these errors were encountered:
Environment
Bug description
I have an IDN domain (with an umlaut) as host in my ejabberd config. Certificates are issued for the domain in punycode. File upload via mod_http_upload from Conversations 2.9.6 to the internal fileserver would fail with standard configuration, so here is what I tried:
Working
1
host: punycode
put_url: @host@
comment: Works, but nobody wants JIDs in punycode.
2
host: unicode
put_url: punycode
Failing
1
host: unicode
put_url: @host@
2
host: unicode
put_url: unicode
In the failing cases, ejabberd logs that it cannot handle a put request to the host (written in punycode). From the discussion in the Conversations MUC i assume that while Conversations sends http headers (correctly) with punycode, ejabberd should transform them to unicode when interpreting them as host.
The text was updated successfully, but these errors were encountered: