I try to addon a domain via cpanel with the new greek TLD .ελ. (It does contain greek characters).
Ι am going to
cpanel > domains > Addon Domains
and in the first input "New Domain Name", when I add the new domain (eg: mydomain.ελ), I get the error:
That is not a valid domain.
Ι think the problem is with the greek characters in the TLD.
Are these cpanel issues?
Or is this a server configuration issue?
Any help would be appreciated.
In case of IDNs many tools are not updated to handle them and need to manipulate the encode form.
So in your case try to use xn--qxam instead as TLD, it should at least be accepted, but other things may not work later on.
If the other part of the domain has non ASCII characters too, you will need to encode it. Search for IDN encoding or punycode.
Related
this is my first question here, so I will try my best.
I am trying to get the protocol and the FQDN (fully qualified domain name) from a bunch of domains, i.e. get https://es.aliexpress.com from aliexpress.com.
I have tried Selenium webdriver, but it takes too long to compute all the domains (even with short timeouts and blocking images).
I am asking if someone knows a way to do this without loading the content, something like wget but only for the URL.
Thank you for reading.
Not really...
First of all, http and https have nothing to do with domain names. Those are transfer protocols.
Ignoring that part, what you are calling FQDN are often generated at the time you access them.
For instance, many websites redirect the browser from a desktop site to a mobile version (the typical m.something.com) based on your User Agent string. Which mean www.something.com and m.something.com are both valid answers
In the example you gave, aliexpress.com, prepended es. which means there is most likely some code on the server that reads in either your location (based on IP address) or a locale setting in your browser to direct you to the es version of the website as opposed to the en or dk version.
These changes can be done via an .htaccess file in the root folder of the website, or via back end code.
Google Chrome itself automatically tries to add www. if it looks like you typed a URL into the everything bar.
It's also possible that the URL is one giant redirect. Some websites buy up extra domain names that all redirect to their core site. So even if you input xyz.com you'll end up at abcd.com.
There is no algorithmic way to go from a base URL to what you're calling the FQDN.
P.S. Here is an article about what FQDN means.
I have migrated magento code base from one machine to another, so web server configuration is different, I do not have access to working machine.
Problem
www.example.com has internal file load failures due to missing slash after domain name.
Example of internally failing URLs
www.example.comjs
www.example.comcss
I have tried nginx and apace, both give same issue. I do not know how can i fix it. Please help for any server nginx or apache.
Open the stores DB using a MySQL viewer.
go to table name "core_config_data".
find record with name "unsecure_base_url" and another called "secure_base_url"
make sure the site is written in this format http://example.com/
make sure you have a slash after the domain name.
Good Luck!
According to RFC 2606 (1999) the TLD .localhost is reserved for use for testing locally.
The goal is to configure a preview site to run locally using the TLD .localhost, e.g. http://example.localhost
The problem is that when I use Chrome or Safari to access a '.localhost' TLD it searches google for example.localhost instead of treating it as a proper address. This is after configuring the hosts file to point back to 127.0.0.1.
Am I misunderstanding the usage of this reserved TLD? Is there a way to configure this to work properly?
.localhost is not an existing, delegated TLD, which is why your browser doesn't find it.
What RFC 2606 says is that .localhost (along with .test, .invalid and .example) will never be a delegated TLD, so you can safely use that name for your own, local, purposes. That is, if you want to set up a private TLD for internal use, that TLD can be safely named .localhost without the risk of a future collision with a globally assigned name.
You can add http:// first. Write http://yolo.localhost in your address bar and not yolo.localhost, then it will work.
See answers here for more information: Chrome browser doesn't like a domain with .loc TLD (for localhost domain testing) without http:// - how to fix?
I've found myself in a situation where I have to use different domains for the same site.
It's a multilingual website that uses the path for the language so I have something like:
mysite.com/en
mysite.com/es
mysite.com/fr
mysite.com/ru
What I need is something like
mysite.com/en
misitio.es/es
monsite.fr/fr
bladimir.ru/ru
It's an Apache server. We enabled domain aliases and if I enter misitio.es the server redirects the web browser to mysite.com/es but showing misitio.es in the url.
What I would need is each domain to work on their own, not redirecting me, sharing all the content and source code. There should be no differences neither in files or in the database, and the htaccess should be configured to redirect each language (/es, /en, /fr, /ru) to its respective domain (*It's the last thing to do, we have not changed thw htaccess file yet).
I've found this guide for multisites in drupal, but it explains how to build a multisite from zero and my website is already in production, also, I'm not sure on how does it apply to my specific problem.
Is it possible to achieve what I need?
Any advice would be helpful.
I run an Expression Engine site that will load an article page regardless of any made up sub directory names typed into the address bar.
For example all these addresses:
http://hellothere.example.com/health/mental/depression
http://cats.example.com/health/mental/depression
http://dogs.example.com/health/mental/depression
http://www.batman.example.com/health/mental/depression
http://www.1.2.3.4.5.6.example.com/health/mental/depression
Will load example.com/health/mental/depression
Obviously, this is less than ideal for SEO since I've got a potentially unlimited number of duplicate URLs.
I am trying to figure out how to use htaccess to strip anything before example.com and replace it with just www.
Any help would be appreciated!
You can not do this with htaccess. The way to do this is to set up a wildcard dns record so that all requests (*.example.com) are all directed to the same server.
See http://codex.wordpress.org/Configuring_Wildcard_Subdomains