Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 240
  • Last Modified:

image hosted on another website

want an image.jpg to be hosted on website.com
but I want to write <img src="website2.com/image.jpg">

and see that image
0
rgb192
Asked:
rgb192
  • 5
  • 4
1 Solution
 
MatthewPCommented:
Shouldn't be a problem, make sure you start the link http:// or https:// or the browser will interpret it as a local request, it needs to be <img src="http://www.website2.com/image.jpg"> (with or without the www as applicable to that site)
0
 
rgb192Author Commented:
but image is on website.com

not website2.com

I want only website2.com to be visible
0
 
MatthewPCommented:
This sounds like a strange request, why do you want the html source to point to somewhere else? At the end of the day being html the url for the image has to result in the image being sent back one way or the other, either that or the image not being displayed.

Could you explain what you are trying to achieve at the end of the day?



0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
rgb192Author Commented:
i am moving website.com to another host and I dont want the website to go down and have no image

I would rather have a pointer image
0
 
MatthewPCommented:
Do you mean you are updating the nameservers and want to ensure that a holding page is displayed whilst the nameservers are being updated?
0
 
rgb192Author Commented:
yes
0
 
MatthewPCommented:
If that is the case, if you move website.com then it won't be able to display the html to tell it to get the image from website2.com if it goes down so that's still not the way to do it. Your best bet is to have your copy of the site on the new host set up and working ready and just do it. Nameserver transfers seem to happen a lot quicker than the 24/48 hours they used to take.

The way to stop this happening is to point your web site using the DNS records rather than the name servers at your host, so you point the A record, www record, MX records separately. This doesnt take time to update as theres no nameserver change if you update them, however if you've already got the nameservers pointed elsewhere theres not a lot you can do in that case.



0
 
rgb192Author Commented:
thanks
0
 
MatthewPCommented:
No problem.

If it is likely nameservers will change in the future be sure to understand DNS from what I said above, research it a bit too it can be complicated if you don't understand it, also you can get managed DNS from a provider like http://www.dnsmadeeasy.com/ - they will host your own nameservers (see Vanity DNS section) and from there you can point the DNS records to various places and still use your own nameservers if you really need that. Will stop down time in the future.

I've had to do the nameserver updates before and generally pick a time when usage is low - overnight maybe - and put a message up a day or 2 before hand saying that server maintenance is happening on the night of xx/xx/20xx, you may experience some temporary interruption in service etc." or something. If you run a mailing list let them know in advance too. Also, last time i did this it transferred in about 2 hours, does seem to be faster these days.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now