When connecting to ws://my-app.com/websocket, it fails with a 301 error (moved permanently).
This was caused by having the force ssl enabled.
You can use CloudFlare's page rules to redirect your non-https traffic to https and disable the Galaxy option.
Try using wss:// instead of ws://.
Related
I have setup a nginx proxy to pass https url to internal http neo4j web. I can reach the neo4j login page without any issue, but I am forced to use the neo4j+s/bolt+s interface.
Just wondering how I can configure nginx to remove any ssl related info via proxypass module, in order to login in neo4j with ws, no wss?
Thanks,
Chance
I managed to get rid of wss by adding another nginx proxy to set the https url as upstream server in location.proxy_pass. It won't show wss/neo4j+s/bolt+s any more once you visit the web by the http url. Hopefully it will help for anyone has the similar issue as me.
Why can't I access any of my local development sites anymore? Firefox and Chrome both redirects to HTTPS (localhost/site becomes https://localhost/site and throws an error) ...
I'm not going to set up SSL on my localhost development machine ... How would I prevent ALL browsers from redirecting to HTTPS?
Auto redirect http to https is normally caused by installation of a new plugin or certificate.
Check out this question for how to solve it.
I am disabling all http access and want to return an error code to indicate that http is disabled and use https instead.
what is the best error code response for that request?
400 Bad Request
403 Forbidden
There's not much value in listening on port 80 unless you're either going to serve up content or point clients to somewhere else.
Either issue a 301 Moved Permanently redirecting to https (Redirect http to https in default.aspx) or do not listen on port 80.
403.4 should be the best, as IIS returns exactly this to client side if HTTPS is required,
https://support.microsoft.com/en-us/kb/943891?wa=wsignin1.0
Having problems accessing the admin over https when it's setup behind CloudFront Flexible SSL.
The admin works fine when accessing over http, but as soon as I change to secure https it ends up in a redirect loop.
I'm adding the following line to wp-config.php to force SSL in the admin.
define('FORCE_SSL_ADMIN', true);
This is due to the fact that CloudFlare's Flexible SSL operates as a reverse proxy and connects to the WordPress installation via http. Wordpress thinks you're connecting via http and does a redirect to the https resource. The browser requests the https resource from CloudFlare and CloudFlare again requests the resource over http from the WordPress server, resulting in another redirect.
Fortunately there's a solution. CloudFlare sends an http header X-FORWARDED-PROTO that is the protocol used in the connection from the browser to the CloudFlare server. We can use this to tell WordPress that even though the request is happening over http, the link to the browser is over https.
In the wp-config.php file add the following line:
if ($_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') $_SERVER['HTTPS']='on';
It's also crucial that the above line comes before the following line:
require_once(ABSPATH . 'wp-settings.php');
After making that modification the redirect loop will stop and you'll be able to use the admin again.
This ultimately applies to all reverse proxy servers, not just CloudFlare.
In my case we getting this problem because I configure CloudFront origin incorrect.
cloudfront-> origin -> Origin Protocol Policy -> Match Viewer
after this setting my website working fine
in my case, another source of problems was (I know sounds silly) the DefaultRootObject.
I had this error on my CloudFront and WordPress and was the issue of my Too Many Redirects nightmare. I'm posting that because someone falls into the same stupid error like me.
Cheers
I want to disable https and want to access a site by http (for experimental purposes).I am using firefox on ubuntu 12.4. I tried by disabling SSL in browser.But then i am not able to access sites with https.
How can i do this?
Some sites, require using https (SSL) for accessing them. The site you try to access would probably redirect you to https (SSL), even if you decide to use http. In that case, you cannot disable the SSL use from your browser, because it is a demand from your target site.
Hope I helped...