requested an insecure XMLHttpRequest endpoint #1366

New Issue

devdev · 2023-01-23T10:05:12Z

devdev commented

2023-01-23 10:05:12 +00:00

Description

Hello,
After an upgrade has been done from 0.18.1 to 0.20.1, it shoot an error during "logout" of vikunja user account.

The error message is:

Mixed Content: The page at
'https://site_link/with_token'
was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint
'http://site_link/api/v1/info'.
This request has been blocked; the content must be served over HTTPS.

NOTE: In my vikunja application, i used openid authentification. And it seems all ok in my config.yml

Vikunja Frontend Version

0.20.1

Vikunja API Version

0.20.1

Browser and version

Chrome est à jour Version 109.0.5414.75 (Build officiel) (64 bits)

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

Error Message:
Mixed Content: The page at
'https://site_link/with_token'
was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint
'http://site_link/api/v1/info'.
This request has been blocked; the content must be served over HTTPS.

### Description Hello, After an upgrade has been done from 0.18.1 to 0.20.1, it shoot an error during "logout" of vikunja user account. The error message is: > Mixed Content: The page at > 'https://site_link/with_token' > was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint > 'http://site_link/api/v1/info'. > This request has been blocked; the content must be served over HTTPS. NOTE: In my vikunja application, i used openid authentification. And it seems all ok in my config.yml ### Vikunja Frontend Version 0.20.1 ### Vikunja API Version 0.20.1 ### Browser and version Chrome est à jour Version 109.0.5414.75 (Build officiel) (64 bits) ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots Error Message: Mixed Content: The page at 'https://site_link/with_token' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://site_link/api/v1/info'. This request has been blocked; the content must be served over HTTPS.

devdev added the

kind/bug

label 2023-01-23 10:05:12 +00:00

konrad commented

2023-01-24 21:49:24 +00:00

This probably happens because the frontend tries to find the correct api url. What did you configure as API?