Share link doesn’t use domain with german umlaut but punycode domain
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
My Nextcloud server has an IDN domain with an “ö” in the URL.
it works fine but every time I create a share link, it uses the punycode domain ( https://xn–…-zxa.net/s/…) instead of the correct domain with ö.
Because this is very ugly, i change it by hand each time.
The configuration contains both domains as trusted domains, the one with ö is the first one.
I tried setting overwrite.cli.url and overwritehost but it doesn’t make a difference.
I’m running:
nextcloud 12.0.1~jessie
Debian Jessie 8.9
nginx 1.6.2-5+deb8u5
php 5.6.30+dfsg-0+deb8u1
Is there a way to rewrite the share link or configure it correctly?
Thank you very much!
Florian
PS: The nextcloud windows client doesn’t like hostname in my SSL cert which I had to create with a punycode because let’s encrypt doesn’t seem to support IDNs correctly. But it can be ignored easily.
Steps to reproduce
- setup nextcloud on a server with a international domain name/IDN
- create a share link
- the link contains not the IDN but the punycode domain
Expected behaviour
The share links should use the IDN, in my case with an "ö".
Actual behaviour
The share links contain the punycode domain https://xn–…-zxa.net/s/…
Server configuration
Operating system: Debian Jessie 8.9
Web server: nginx 1.6.2-5+deb8u5
Database: MariaDB
PHP version: php 5.6.30+dfsg-0+deb8u1
Nextcloud version: nextcloud 12.0.1~jessie
Updated from an older Nextcloud/ownCloud or fresh install: updated from 11
Where did you install Nextcloud from: http://apt.jurisic.org/debian/
Signing status:
Signing status
No errors have been found.List of activated apps:
App list
- activity: 2.5.2 - audioplayer: 2.0.2 - bruteforcesettings: 1.0.2 - comments: 1.2.0 - contacts: 1.5.3 - dav: 1.3.0 - federatedfilesharing: 1.2.0 - federation: 1.2.0 - files: 1.7.2 - files_pdfviewer: 1.1.1 - files_sharing: 1.4.0 - files_texteditor: 2.4.1 - files_trashbin: 1.2.0 - files_versions: 1.5.0 - files_videoplayer: 1.1.0 - firstrunwizard: 2.1 - gallery: 17.0.0 - groupfolders: 1.1.0 - keeweb: 0.4.0 - logreader: 2.0.0 - lookup_server_connector: 1.0.0 - news: 11.0.5 - nextcloud_announcements: 1.1 - notes: 2.3.1 - notifications: 2.0.0 - oauth2: 1.0.5 - ocsms: 1.12.0 - password_policy: 1.2.2 - provisioning_api: 1.2.0 - serverinfo: 1.2.0 - sharebymail: 1.2.0 - survey_client: 1.0.0 - systemtags: 1.2.0 - tasks: 0.9.5 - theming: 1.3.0 - twofactor_backupcodes: 1.1.1 - updatenotification: 1.2.0 - workflowengine: 1.2.0Nextcloud configuration:
Config report
``` "system": { "instanceid": "ocmu739zt14y", "passwordsalt": "***REMOVED SENSITIVE VALUE***", "secret": "***REMOVED SENSITIVE VALUE***", "trusted_domains": [ "***REMOVED SENSITIVE VALUE***" ], "datadirectory": "\/daten\/www\/nextcloud\/data", "overwrite.cli.url": "***REMOVED SENSITIVE VALUE***", "dbtype": "mysql", "version": "12.0.1.5", "dbname": "nextcloud", "dbhost": "localhost", "dbport": "", "dbtableprefix": "oc_", "dbuser": "***REMOVED SENSITIVE VALUE***", "dbpassword": "***REMOVED SENSITIVE VALUE***", "logtimezone": "UTC", "installed": true, "maintenance": false, "loglevel": 2, "overwritehost": "schr\u00f6ck.net"</details>
**Are you using external storage, if yes which one:** no
**Are you using encryption:** no
**Are you using an external user-backend, if yes which one:** no
### Client configuration
**Browser:** Chrome
**Operating system:** Win10
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start by reproducing share-link creation with an internationalized domain and inspect how overwritehost, overwrite.cli.url, and trusted_domains feed the generated URL. Done means generated share links use the configured IDN rather than its punycode form, with regression coverage for the reported setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100