Backend error with firefox using a domain like relaunch.adomainwithöinname.de

[neos-bot]

Jira issue originally created by user beo6:

Using a Domain like relaunch.adomainwithöinname.de and accessing the backend with Firefox (Developer Edition) [tested with Version 40.0a2]

the backend shows a couple of errors and the Hide after, hide before and all image fields in the right side only show the label, so editing them is impossible.

Using either Chrome or accessing it with the Server IP-Address instead of the domain prevents the errors and all fields are accessible.

Possibly related to [http://stackoverflow.com/questions/10607370/require-js-text-plugin-adds-js-to-the-file-name] ?

Atachements:

Jira-URL: https://jira.neos.io/browse/NEOS-1302

[neos-bot]

Comment created by beo6:

Also tested it with creating a subdomain of a domain without special character and it works there too. So it must be an issue with the "new" domains that can contain special characters together with firefox.

[jhinzmann]

I have a Neos 3.1.1 which runs on an domain with an umlaut (ü) and I can reproduce this issue.

I tried the Neos backend with the following browsers: Firefox Version 54.0.1 -> throws Microsoft Edge 38.14393.1066.0 -> throws Internet Explorer 11.1480.14393.0 -> throws

Chrome 59.0.3071.115 -> just works

Requirejs tries to load the following files, which result in 404s:

• [domain]/_Resources/Static/Packages/Neos.Neos/JavaScript/Content/Inspector/Views//NodeInfoView.html.js?bust=5a9c59cec3de
• [domain]/_Resources/Static/Packages/Neos.Neos/JavaScript/Content/Inspector/Editors//DateTimeEditor.html.js?bust=5a9c59cec3de
• [domain]/_Resources/Static/Packages/Neos.Neos/JavaScript/Content/Inspector/Editors//ImageEditor.html.js?bust=5a9c59cec3de
• [domain]/_Resources/Static/Packages/Neos.Neos/JavaScript/Content/Inspector/Editors//ImageEditorCrop.html.js?bust=5a9c59cec3de
• [domain]/_Resources/Static/Packages/Neos.Neos/JavaScript/Content/Inspector/Editors/FileUpload.html.js?bust=5a9c59cec3de

With Chrome the files are loaded without the .js part. Since this bugticket is open for more than 2 years, maybe someone has a workaround or something?

[mhsdesign]

Hello from the future ^^ I dont think, that this is still an issue - since the React rewrite + a lot of browser updates. So i think this can be closed?