CODEWITHSUNDEEP
asp.netperformanceiiscachingbrowser
tugberk
tugberk

Reputation: 58444

serving images from one domain for multiple websites

we have nearly 13 domains within our company and we would like to serve images from one application in order to leverage caching.

for example, we will have c1.example.com and we will put all of our product images under this application. but here I have some doubts;

1- how can I force client browser's to cache the image and do not request it again?

2- when I reference those images on my application, I will use following html markup;

<img scr="http://c1.example.com/core/img1.png" />

but this causes a problem when I run the website under https. It gives warning about the page. It should have been used https//c1.example.com/core/img1.png when I run my apps under https. what should I do here? should I always use https? or is there a way to switch between auto?

I will run my apps under IIS 7.

Upvotes: 2

Views: 427

Answers (2)

Pauli &#216;ster&#248;
Pauli &#216;ster&#248;

Reputation: 6916

Yes you need to serve all resources over https when the html-page is served over https. Thats the whole point of using https.

If the hrefs are hardcoded in the html one solution could be to use a Response Filter that will parse all content sent to the client and replace http with https when necessary. A simple Regular Expression should do the trick. There are plenty of articles out there about how these filters are working.

About caching you need to send the correct cache-headers and etag. There are several of questions and answers on this on SO like this one IIS7 Cache-Control

Upvotes: 1

John Chadwick
John Chadwick

Reputation: 3213

  1. You need to use HTTP headers to tell the browser how to cache. It should work by default (assuming you have no query string in your URLs) but if not, here's a knowledge base article about the cache-control header:

    http://support.microsoft.com/kb/247404

    I really don't know much about IIS, so I'm not sure if there are any other potential pitfalls. Note that browsers may still send HEAD requests sometimes.

  2. I'd recommend you setup the image server so that HTTP/S is interchangeable, then just serve HTTPS Urls from HTTPS requests.

Upvotes: 1

Related Questions