HTTP Upload fails with managed backend

@MarcelWaldvogel

Chrome/62.0.3202.97

Console error message:

Failed to load https://userdata.[DOMAIN].jsxc.ch/f3117686f6c2d7970fae9c263771a59e859cc3fb/YC0Udmaea8LEyqGEtQYYATl7Kl63FKQXbFujk2z5/Dez-2017.md.html: Response to preflight request doesn't pass access control check: The 'Access-Control-Allow-Origin' header contains multiple values '*, *', but only one is allowed. Origin 'https://[DOMAIN]' is therefore not allowed access.

Request:

Request URL:https://userdata.[DOMAIN].jsxc.ch/f3117686f6c2d7970fae9c263771a59e859cc3fb/YC0Udmaea8LEyqGEtQYYATl7Kl63FKQXbFujk2z5/Dez-2017.md.html
Request Method:OPTIONS
Status Code:200 
Remote Address:193.197.88.169:443
Referrer Policy:no-referrer-when-downgrade

Response header:

access-control-allow-headers:Content-Type
access-control-allow-headers:Content-Type
access-control-allow-methods:OPTIONS, HEAD, GET, PUT
access-control-allow-methods:OPTIONS, HEAD, GET, PUT
access-control-allow-origin:*
access-control-allow-origin:*
content-length:1
content-security-policy:upgrade-insecure-requests
content-type:text/plain
date:Sat, 30 Dec 2017 20:08:59 GMT
server:Apache/2.4.29 (Ubuntu)
status:200
strict-transport-security:max-age=31536000

[koarlmichael]

Tried it with 3 users with OMEMO encryption in the group chat and it works perfectly with Conversation on Android. Just wait for OMEMO in Nextcloud Chat in the Browser 😃 Thank you and I think you can close the issue.

[koarlmichael]

I’m testing the group chat with OMEMO again tomorrow. Do not think it’s on the server.