Tag Info

New answers tagged

3

http://www.example.com/ and http://www.example.com are the same URL. Whether or not the trailing slash is shown in the browser address bar is purely cosmetic - when the request is sent to the server the slash will be included. (http://www.example.com/foo and http://www.example.com/foo/ on the other hand are different URLs.) If the site you're working on is ...


1

I had the same issue, and the Requests are definitely hitting the server for it to respond with the 304 status - I'm sending the 304 via some C# and for sure it hits the server.. I only had Cache-Control: private set. No max-age and no Expires It operated as expected; hit the server with the If-Modified-Since where I test the value compared to what I ...


1

From my understanding and experience it seems to me perhaps you've misunderstood how CDN caching works: From the example you've given, the CDN would not ask your web-server when the file was last modified because you've already told it that the file has expired and will therefore need to be re-fetched anyway. Web browsers will only send an ...


0

You should keep in mind that a 304 Not Modified header still requires a request going through to your server. You properly won't want to send 304 Not Modified headers, you most like want to send a cache expire header, so that the browser doesn't even try to request the resources again. That of course only relevant for static resources (images, scripts ...


1

change your htaccess file code <IfModule mod_headers.c> Header add Access-Control-Allow-Origin "*" </IfModule> when you write Header add Access-Control-Allow-Origin "http://skin.cdn.com" this, you can only access this domain. not http://domain2.com. * this allow you to all domain.



Top 50 recent answers are included