A customer asked to be able to call my web app from his domain for hiding my domain name.
I remembed that several years ago it was used to use an hidden iframe ... is there a more "modern" solution?
The only better solution is to actually host the site on the domain that you want it to appear on.
He might want to consider setting his DNS to point a subdomain at your servers if you are unwilling to install the application on his.
Related
I have a blog at http://www.futuristiccreativity.tk but if I type it without www on the browser, i.e., http://futuristiccreativity.tk it shows up error loading the blog.
Is there any possible solution for this redirection?
Well, this is one of the most common problems of bloggers who use blogger for publishing their content and set up a blog. I too suffer from this the most.
Recently, I made a way out of this problem. Though Google support tells to add A records which point to these IPs to redirect to the www version of the site, that doesn't work for me:
216.293.32.21
216.293.34.21
216.293.36.21
216.293.38.21
But a simple way out is, remove all these A records and have just one record.
Now the solution, Go to your domain registrar dashboard and add an A record whose host is # and points to 174.129.25.170 IP. And all your problem will be gone within some time(it may take up to 24hrs for DNS to migrate the preferences)
Check out my blog post to have a better understanding.
Okay, here's the situation. I've had a bluehost account for several years and am happy enough with it I'm unwilling to move without a really good reason. However, I'm finding more and more that the best solution to the main use for one of my domains is to have a fairly simple rails app running to cover that.
The rails app could easily be front-ended by two forms on the landing page, each with a couple of follow-up pages, but I want the URL always to show "mysite.com" rather than "myapp.heroku.com". I also want to continue to use my email addresses with this site. I don't expect the app to see heavy usage, and am unlikely to go over the 750 hr/mo free time on heroku.
I currently use Rails 3, and would likely have trouble stepping back to rails 2 in my thinking. I'm also not very good at programming in rails, or anything else for that matter, so I'd like not to confuse myself any more than necessary.
So what's my solution here? Transfer the whole domain to Heroku? Embed partials of the app in the landing page? Can I keep email addresses working with Heroku? Can I transfer just the www.mysite.com to heroku, but have everything else involved with the domain hit bluehost?
I'm open to advice.
Heroku doesn't provide any email hosting/sending itself - so you either bring your own or use one of the Heroku addons like SendGrid for sending mail from your application.
Of course, you can just leave you email etc with Bluehost provided that you can modify the DNS and change your www record to be a CNAME to proxy.heroku.com (after you've added the custom domain addon to your Heroku application)
I just did this with blue host and heroku where I hosted my app on heroku and wanted to keep email on blue host. I am using DNS Made easy so your mileage may vary but I had to create an A record pointing to the ip address 69.89.31.63, you name the A record mail.yourdomain.com
and then create an mx record pointing to 69.89.31.63. I am on the cedar stack.
I am developing a login and account system for use with an existing website, this will run on a subdomain under the main site url.
I would like to use a subdomain that is generic enough so it isn't tied to an account system but not off-putting to users.
I was thinking of www2 but I am concerned people will see this and think its not "legitimate".
Thanks
Some more context.
The new site is currently used for the login and account system but I will eventually migrate the whole website to the new system, this means the services and pages served by the subdomain will very a lot so it can't be specific to one thing.
Try something generic in the interest / knowledge domain of the existing website. What does the existing website do or provide? This can help you determine a proper subdomain.
Some generic examples:
info.domain.com
account.domain.com
auth.domain.com
app.domain.com
to.domain.com
Providing a better subdomain is going to require some more context.
This question already has an answer here:
Closed 12 years ago.
Possible Duplicate:
What’s the point in having “www” in a URL?
Hello, I have little to no experience owning a website but I am willing to learn all that there is to this process. However I am frustrated because I am constantly blocked by simple problems.
I just uploaded my first index.html page which is basically a background color and a title image. I put my favicon in the public_html directory right next to index.html. I immediately notice that it does not work. I also notice that I have typed http://website.com in the URL bar. I type "www" before "website" and the favicon shows up. I hit back and the favicon is blank again. What is the difference between the non-www version of the site and the www version of the site? Why does the favicon not show up? What other differences are there? Should I disable the non-www site like many professional sites seem to do? How do I do this? What are the advantages and disadvantages, if any?
Thank you.
The www-subdomain is just a convention amongst websites to indicate this address points to a World Wide Web server.
For example,
google.com is the top domainname of
the Google company.
www.google.com indicates this is the
domain name for the World Wide Web,
ftp.google.com indicates this is
probably an ftp-server.
But as it is just a convention, and the average user uses the internet mainly for www, most servers configure their http://domain.com to be aliases to http://www.domain.com.
Why the favicon on your site only shows up for the www-version and not for the topdomain, depends on your html and your server configuration. Can you post some code or link to your site?
The fully qualified domain names are different. So they are different websites.
Usually the two hostnames will point at the same IP address, and the server will be confiured to either serve up the same content for both or redirect from one to the other.
Redirecting from on to the other (and which way round you do it doesn't really matter) is generally considered good practice as it lets you be consistent (and saves you from issues such as XHR requests to a specific hostname breaking when used on the alternative).
The favicon not working is likely caused by your browser having cached that http://www.example.com/favicon.ico didn't exist and it not having yet checked again. http://example.com/favicon.ico, OTOH, is a different URI so it would have checked it the first time you went there (which was after you created the icon file).
Typically most of the server domain manager software like Cpanel and Plex are configured to serve same site for both domains. Cpanel do have a public_html and www separately, but same content.
We are trying to streamline the process of showing clients their websites whilst in development without the need to change absolute paths etc.
We mostly develop locally and change our hosts files to reflect the domain name, when we are ready to show the client we copy the files to www.client.com/dev but I'm looking for a better method, any suggestions that can make this process smoother and faster would be great.
If you always host the site on a separate domain and not in a subdirectory, you will never have to change absolute paths. So instead of hosting a site in development at www.client.com/dev try dev.client.com. Another option would be to use client.yourcompany.com.
Also try to protect the site in development with HTTP basic authentication. This is easy to set up in most web servers, without changing your web application. Also, if the content is even remotely sensitive in any way, use HTTPS as well.
Alternatively, let them simply come over to your office and present it to them (or go to them and present it). The upside is that you have full control over what they will and won't see, and it never has to go online.
Well, we have client.t.uw.ru site which is universally visible.
When it matures, it moves onto www.client.com and is pushed to search engines.
Thus, we have a * DNS entry on t.uw.ru domain which makes it easy.