Tag Info

New answers tagged

1

Both are fine, but the URL path has a slight benefit over subdomains, because the backlink juice would be concentrated on one domain. Managing one domain is also easier than multiple subdomains. In all cases, I would put the id of the question/answer in the url, because it will make the url unique for sure.


0

A sub-folder is much better for SEO. Just read this thread for example. However, if you are finding it takes a long time to get your pages/sub-domains indexed, is it a problem with the authority of your website in general? E.g. does Google trust your domain/crawl the site often. What I'm trying to say is Determine whether Google visits your website ...


0

If you are using IIS, you can add IIS rewrite rules to your web.config to specify which type of robots.txt to return, depending on the subdomain the user (and thus the crawler) is browsing to. You can specify special HTTP_HOST pattern conditions to specify which robots.txt file should be used for which domain. An article which explains this perfectly: ...


1

For 3 reasons. Fast browsing. Modern browsers download resources concurrently from each domain to have faster browsing experience. That's why some of the sites use foobar.com and cdn.foobar.com to split the site assets across few domains. Cookies. Cookies are bad for caching. And they are not needed for serving assets (images, videos, css files etc.) under ...


1

The practical reason is to control sending of cookies. However, this can better handled by setting the correct domain (and path) on the cookies. This will greatly limit the cookie volumes. One of the reasons I have seen is that someone decides to use thisIsAReallyGoodName.com for some reason. It may seem like a good (marketing?) reason at the time. ...


3

Static resources are often served from completely separate domains, when the website uses a naked domain (twitter.com for example). In this case, all the cookies set by twitter.com apply also to subdomains. So, if the static resources were served from cdn.twitter.com, the cookies would also be sent to that domain. This increases the network traffic, and ...


0

You can create a cname with dot notation in it. So you can create a cname which is es.n and point it to the a record and it will take care of what you want. This is done via Godaddy DNS hosting (free usually with all domains)


0

you will not have security risks with these cookies if you set them as http only cookies via ssl connection. This means they are set with the http only flag and then set on a page which is ssl secure. if you have hhtp only flags and secure flags you should be fine. if you want to take it a step further consider using a engrypted key as the cookie and ...


2

To my way of thinking, if the client's browser is compromised then everything is possible. Or in other words : Whether a website is a sub-domain or not does not matter much to security. In any case, if the websites are defined as sub-domains then you should avoid cookies that are defined for the upper-level domain - define the cookies for ...


4

You can add a wildcard DNS record for your domain. Using that, every possible subdomain points at your server. Then your webserver can choose which subdomains have content and which subdomains redirect. The sites that use DNS records to find subdomains won't be able to distinguish the ones that are used from the ones that are not.


2

You can't due to the nature how sub domains work. When adding a sub domain you are adding public records to the main domain and anyone can do a NS lookup or similar to reveal additional information regarding the domain. If you want it private then use an internal domain over a VPN or use the IP address, or better yet just ensure your sub domain is secure ...


0

I would use either sub folders or sub-domains for each franchise location. It would let corporate have easier control over the content and less to manage. Plus an easy way to update all franchise sites if needed. Look at how UPS handles it with each of their stores http://newyork-ny-1492.theupsstorelocal.com/ It also helps with branding, if people aren't ...


0

In my case, the following was working: www.domain.com/subdomain But subdomain.domain.com was not. I realized that my default index was: /subdomain/index.htm. I renamed it to /subdomain/index.html. Now, subdomain.domain.com is working. Note: it should be place to force to look for index.htm too, but I think I can't access to those config files with my ...


0

The typical way to host a new domain or subdomain under Ubuntu/Debian is covered in this tutorial. Here are the basic steps: Create the file /etc/apache2/sites-available/owncloud.example.com.conf with contents based on this template: <VirtualHost *> ServerAdmin webmaster@example.com ServerName owncloud.example.com ...


2

If you have access to the DNS of your domain this should be possible. You can create a subdomain called foo.bar.example.com in your DNS, but of course it must point somewhere, e.g. 127.0.0.1. If you do not have DNS access this is most likely not possible. If your web host allows you to create subdomains, most likely you can add subdomain.subdomain.domain. ...



Top 50 recent answers are included