I never use or see the www. version of my site, as far as I know, unless it happens "under the hood". When I added the https://example.net version, I got an email suggesting I add all versions of my site. So should I add the www. version? What is the benefit of doing this? And if it is the right thing to do, do I add a sitemap with the url of the www. or the non-www. version please?
Should I also add http versions?
Related
I've got a clients site that uses Google Cloud Run and I need to implement some redirects as they have both www. and a non www. version of the site simultaneously.
https://www.example.com
https://example.com
I would like to setup a redirect so that it goes from www. to the non www. version. I know I can't do this at DNS level for this type of redirect so am looking at doing it at a server level. I've checked for documentation on this on Google Cloud run and can't seem to see anything relevant. I've never worked with a client site that uses cloud run before, but have a good idea of how I'd go about doing this on a website that uses Apache or Nginx.
Does anyone know if there is a specific file where I should be implementing redirects within the Cloud Run setup?
Thanks,
Adam
You should do this in the code. For example if you were using Python with Flask, you can implement it in your #app.before_request
I just uploaded TYPO3 (10.4.12) from my local to a server and its only reachable when not using www.
Without it the page loads fine, but when using www. it just shows a blank page. It uses the standard htaccess without any modification. Server Host says its TYPO3 settings. But I can't find this anywhere? How can I make it accessible with www.?
blank screen in an production setting means you have an error. look into the server log or switch temporarily to develop mode to identify the error.
I assume a wrong redirect in the domain configuration.
I have website hosted on zeit. I bought domain, but it can only be accessible via https://www.example.com but when i try to enter my websites name to google adsense it keeps downgrading to https://example.com, so, because of that verification always fails. How to solve this? How to change dns settings to redirect https.. to https://www..? Or is it possible to prevent downgrade to https? I'm basically failing first step of adsense registration.
I am developing a Telco application (Dyanamic Web application project to send and receive sms) using Eclipse & tomcate version 7
When I try to run it on
http://localhost:8080/SMS1
It gives an error message HTTP-ERROR-CODE:302
What should I do to resolve this error
This is the link to Application and video tutorial what I am following
https://drive.google.com/file/d/0B3VmCeqDC7SDcFZaWVZhRUNmaTQ/edit?usp=sharing
HTTP code 302 is a standard "redirect" message--that is, it tells your web browser that the page was moved and where the new page can be found. I'm guessing whatever you're using as a web browser (Eclipse?) just doesn't handle that type of redirect. Try using a standard web browser like Chrome or Mozilla to see if that helps...
Also a guess, but the redirect may be trying to move you to HTTPS instead of HTTP, and your certificates may not be set up properly, or the port isn't enabled, or there may be some other problem with your HTTPS configuration. If the app is supposed to work over HTTPS, try going directly to the HTTPS version of the link to see if that's the real issue.
A third guess is the app may be trying to redirect you to a login page if you're not logged in, and maybe it can't find it. I'd need to know a lot more about the built product and I really don't want to mess with some guy's shared Eclipse project. Tell them to use a build tool!
Recently I've set up the ClearCase Remote Client (an eclipse plugin) to work through SSL, so instead of an http URL, it follows an https URL.
However, this breaks the access to the Update Site, returning an error that the site has a "Premature End of File" error.
My question(s) are this...
Is there a problem with Eclipse accessing Update Sites that have been reached through a redirect rule?
or
Is there a problem accessing Eclipse Update Sites through a SSL connection?
Any tips or anecdotes would be awesome!
EDIT : The link works via the browser, in terms of a redirect, but not in Eclipse when I attempt to access the same directory via the Update Site tool.
It seems to be a known issue for other plugins as well
What is the "description site" looks like in your eclipse p2 configuration ? Does it include https as in:
<description url="https://<host_name>/<update_site>/">
Project Update Site
</description>
Just do be sure, you did Enable HTTP proxy connection ?
(General->Network Connections)
Although VonC made a really valiant effort, my answer or workaround has been to configure RWP to use SSL for the CCRC Server, and simple Port 80 for the Update Site with a redirect for any users who are still pointing at the old URL.
I am still unsure why it doesn't work in Eclipse with SSL though.