Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mixed Content , but requested an insecure XMLHttpRequest endpoint #17

Open
scenaristeur opened this issue Nov 8, 2017 · 2 comments
Open

Comments

@scenaristeur
Copy link

I want to use EyeServer from my webApp https://spoggy0.firebaseapp.com/ ( clic the "cat" icon to toggle to the chat/graph page, then clic on "..." icon to open "Eye reasoner" panel)

Then clicking on "Execute Eye" , the app send this data :

data=@prefix : <ppl#>.
 
:Spoggy :type :WebApp.
:Spoggy :developpeur :David.
:David :connait :Bob.
:Spoggy :hasPart :Graph.

&data=@prefix : <ppl#>.
         { ?a :connait ?b }
 =>
         { ?b :connait ?a .
           ?a :type :Personne.
           ?b :type :Personne}.

          {?c :developpeur ?d}
          =>
          {?d :type :Developpeur}.

          &query={ ?a ?b ?c. } => { ?a ?b ?c. }.

to the eye endpoint : http://eye.restdesc.org/

but i got this error message :

iron-request.html:331 Mixed Content: The page at 'https://spoggy0.firebaseapp.com/' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://eye.restdesc.org/'. This request has been blocked; the content must be served over HTTPS.

It seems that the problem could be resolve, if the endpoint server could provide "https" instead that "http" as describe here https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content/How_to_fix_website_with_mixed_content.

Could you migrate to https or do I have to find another solution. ?
NB :
(my code works correctly on localhost)
(don't be afraid with the error : "GET https://spoggy0.firebaseapp.com/socket.io/?EIO=3&transport=polling&t=L-TLMwH 404 ()" , this is another problem (firebase don't accept socket.io ;-\ )

@RubenVerborgh
Copy link
Collaborator

We'll indeed need to migrate to HTTPS. Unfortunately, the service is currently running on an old server, for which the usual solutions (Let's Encrypt) are not that straightforward.

I'll investigate moving this. In the meantime, you could look for an HTTPS proxy or set one up at firebaseapp.com.

@RubenVerborgh
Copy link
Collaborator

@joachimvh Need to think about HTTPS as well for the new server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants