I am in the process of transitioning a fairly sizable website to https. However, I have found different information regarding site maps.
Should I switch my site map to https BEFORE I launch https?
Should I switch my site may to https AFTER I launch https?
Should I have two site maps (one with http protocols and the other with https)?
I am very concerned with a possible hit to SEO after https goes live so any and all suggestions would be appreciated!
Related
We are trying to get a google site to run behind a proxy.
Spoke to a google support specialist and they said its possible, did not give any documentation and said to ask here.
A google website behind a nginx-proxy or Apache.
This proxy will be used to redirect traffic based on url.
The github web site is awfully fast and considering it's serving a ton of requests I've been wondering if github uses a reverse proxy something along the line of varnish or nginx?
I have a website that's serving highly dynamic content just like the github web service and I've been wondering if it's possible to front it with a reverse proxy for better performance.
Currently I'm hosting a client application written in AngularJS on Google Cloud Storage using the configuration described here.
I like this configuration because it acts as a CDN and we don't have to use a dedicated machine to host the frontend files.
The problem is that Google Cloud doesn't support HTTPS for custom domain names, and we want to improve our security standards serving at least the login page on an https domain.
¿Is there anyway we can keep the static files hosted on Google Cloud/some other CDN for fast serving and use an https domain?
Update
For anyone interested, we finally migrated all our CDN with HTTPS requirements to Amazon S3 + CloudFront and it works like a charm.
While Google Cloud Storage does support HTTPS, it does not support HTTPS for custom domain names.
Although you've found a solution not connected with your original question, I'm answering in case someone gets here with the same question like I did.
Google Firebase link is an excellent way to serve websites (and apps) as it is automatically through SSL (https) and Google Edge servers (effectively CDN function). And https will work using your own domain name. You can push your site from your local machine (Node.js needed) or from GitHub, Gitlab, etc. using continuous integration/deploy.
There is a generous free trial plan to try it first, then a reasonable monthly rate to pay as you go as your usage grows. plans
I am trying to block all traffic (I mean all the websites on the internet) and only allow google maps. I am using squid transparent proxy in pfsense.
well, the issue is that it blocks all the websites but allows the https, so everyone can connect to YouTube, Facebook and every website that uses https.
Is there any way to block the httpss websites except one or few?
Thanks!
Well you have 2 ways the 1st way is using WPAD which blocks https but i heard that some androids or some devices dont work as well so I cant tell you how good it works
https://forum.pfsense.org/index.php?topic=93060.0
Or the second way use pfblockerNG like I do and block all the sites that you do not need. Facebook and dropbox easy but youtube seems to come with google so by blocking youtube you block google unfortunately, Hopefully next month E2guardian is going to up and ready for https filtering.
If you need a list for certain sites let me know and I will attach the links to download the IPs
Hope this helps
I want to create a blog for an e-commerce website, but due to data security reasons I don't want to host the blog on the same machine as the website is hosted on. Is there a way to
host it on a separate machine using the sub-domain of blog.domain.com but have it be accessible via the url www.domain.com/blog.
My reasoning is that the content will help with seo better if it uses the same domain.
I was thinking about using mod_rewrite but I'm not sure if it would allow page retrieval from a different website.
It is possible to use the Apache module mod_proxy to make the contents of a server appear to be hosted on another server, and therefore appear to be hosted under a different domain. You might like to take a read of this page which details the Apache configuration directives needed to get it up and running. If that doesn't offer enough options for setting it up how you want it, then you could investigate the "force proxy" option in mod_rewrite, which allows you to send certain rewritten requests through mod_proxy to do the proxying.