Originally created by @oliverbob on GitHub (Jan 15, 2024).
Has anyone experienced this issue?
Mixed Content: The page at 'https://site.com/' was loaded over HTTPS, but requested an insecure resource 'http://site.com/rag/api/v1/query/9c24de82a0286dd099c1ce832f43ff541d2dec98c0c9bdf1db51ebd3cde1b39?query=Tell+me+what%27s+in+this+document.&k=4'. This request has been blocked; the content must be served over HTTPS.
I know that I can always do a reverse proxy like this in Apache (like what I did to all the rest of the sub-directories required by the UI on https:):
But is there a much more simplified way of dealing with https for this UI that can be automated rather than going though the code, for instance, can we have a default self-signed https for this project that can be overridden by certbot?
Thanks.
Originally created by @oliverbob on GitHub (Jan 15, 2024).
Has anyone experienced this issue?
`Mixed Content: The page at 'https://site.com/' was loaded over HTTPS, but requested an insecure resource 'http://site.com/rag/api/v1/query/9c24de82a0286dd099c1ce832f43ff541d2dec98c0c9bdf1db51ebd3cde1b39?query=Tell+me+what%27s+in+this+document.&k=4'. This request has been blocked; the content must be served over HTTPS.`
I know that I can always do a reverse proxy like this in Apache (like what I did to all the rest of the sub-directories required by the UI on https:):
```
<Location "/c">
ProxyPass http://site.com:3000/c/ nocanon
ProxyPassReverse http://site.com:3000/c/
</Location>
```
But is there a much more simplified way of dealing with https for this UI that can be automated rather than going though the code, for instance, can we have a default self-signed https for this project that can be overridden by certbot?
Thanks.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @oliverbob on GitHub (Jan 15, 2024).
Has anyone experienced this issue?
Mixed Content: The page at 'https://site.com/' was loaded over HTTPS, but requested an insecure resource 'http://site.com/rag/api/v1/query/9c24de82a0286dd099c1ce832f43ff541d2dec98c0c9bdf1db51ebd3cde1b39?query=Tell+me+what%27s+in+this+document.&k=4'. This request has been blocked; the content must be served over HTTPS.I know that I can always do a reverse proxy like this in Apache (like what I did to all the rest of the sub-directories required by the UI on https:):
But is there a much more simplified way of dealing with https for this UI that can be automated rather than going though the code, for instance, can we have a default self-signed https for this project that can be overridden by certbot?
Thanks.