How to avoid frames?

S

SpaceGirl

Els said:
SpaceGirl wrote:




Didn't read the rest of the thread, so maybe I'm missing the
point, but it gives the time 6 hours delayed here...

My server is just outside of NYC. I didn't get time to work out how to
get it to work in UTC, rather than Eastern. Perhaps tonight! The time
wasn't the important bit anyway - the page is generated, meaning it
supposedly lacks expiration and creation time stamps in the HTTP header
(etc). I wrote a tiny script that adds the headers to HTTP, so the page
could be ultra-cache-friendly, plus keep search engines happy :)

--


x theSpaceGirl (miranda)

# lead designer @ http://www.dhnewmedia.com #
# remove NO SPAM to email, or use form on website #
 
P

Philip Ronan

(major snip)
(FFS, you didn't need to quote all that did you?!?)

I had a play! http://www.subhuman.net/test.asp :)
Good effort, but invalid.
Should be:
Expires: Mon, 26 Jul 2004 10:32:17 GMT
although having pages expire in the past will make them un-cacheable.
Also invalid. The ETag value should be double-quoted, and should be unique
for every version file. Typically these include hexadecimal representations
of the file size, last-modified date and INode number (= Unix file
identifier). Try and keep it to 32 characters or less.
HTTP time stamps should always be in GMT with the format I mentioned above.
Not strictly valid. I suggest you get rid of " webserver" at the end
Good :)
Are either of these really necessary?

Google for "rfc2616" for help on HTTP headers.

And try testing your pages here:
http://www.ircache.net/cgi-bin/cacheability.py
 
P

Philip Ronan

The ETag value should be double-quoted, and should be unique
for every version file.

... I meant "every version of every file"

i.e., an ETag should only ever be valid for one file on your server, and if
that file ever change, its ETag should also change.

Just putting a time in there is obviously not going to be sufficient.
 
E

Els

SpaceGirl said:
My server is just outside of NYC. I didn't get time to work
out how to get it to work in UTC, rather than Eastern.
Perhaps tonight! The time wasn't the important bit anyway -
the page is generated, meaning it supposedly lacks
expiration and creation time stamps in the HTTP header
(etc). I wrote a tiny script that adds the headers to HTTP,
so the page could be ultra-cache-friendly, plus keep search
engines happy :)

Right! :)
See, that was easier for me than read the whole previous thread
;-)
 
S

SpaceGirl

Philip said:
Good effort, but invalid.
Should be:

Okay, well to be honest I just wanted to see if it works. I can mung the
date into something more valid when I get to play with it at home tonight.

although having pages expire in the past will make them un-cacheable.

yeah I know :) it was just a test.
Also invalid. The ETag value should be double-quoted, and should be unique
for every version file. Typically these include hexadecimal representations
of the file size, last-modified date and INode number (= Unix file
identifier). Try and keep it to 32 characters or less.

ahhh okay. I did google for it but nothing I found made sense. This does :)
HTTP time stamps should always be in GMT with the format I mentioned above.

okay! :)
Not strictly valid. I suggest you get rid of " webserver" at the end

okaydoke. redundent anyway :)

Good :)



Are either of these really necessary?

Hmm I think IIS insists. My sides aren't cookie-free anyway so not that
concerned (although, I'd be interested to find out why the former is
there at all). Cache control... still investigating - it appears to be
something I can control anyway.

Google for "rfc2616" for help on HTTP headers.

okay :) thanks


thanks!

--


x theSpaceGirl (miranda)

# lead designer @ http://www.dhnewmedia.com #
# remove NO SPAM to email, or use form on website #
 
C

Cogito

On the assumption that you haven't got one on your server - and if you have
simply edit it to include the text in the instructions below - open Notepad
and type:

AddHandler server-parsed .html

Press Enter and the save as htaccess.txt

FTP it to your server and change its name to .htaccess - at which point it
will probably disappear from your FTP list because the default is for files
that start with a . to not be shown.

I have done all that you have suggested placed it in a folder an
uploaded it to the space given to me by the ISP. But, it does not seem
to work. In addition, the file .htaccess disappeared after renaming
and now I can't even delete the newly created folder. I guess it's
because of this hidden file.
Is there something else that I'm missing?
 
P

PeterMcC

Cogito wrote in
I have done all that you have suggested placed it in a folder an
uploaded it to the space given to me by the ISP. But, it does not seem
to work. In addition, the file .htaccess disappeared after renaming
and now I can't even delete the newly created folder. I guess it's
because of this hidden file.
Is there something else that I'm missing?

Put the .htaccess in the same directory as your index.html file.

You can see hidden files, including .htaccess - check your FTP help file for
"hidden" - in WSFTP you put "-a" (no quote marks) in the field below the
"MkDir" button and click on "Refresh". Then you can delete the file.
 
C

Cogito

You can see hidden files, including .htaccess - check your FTP help file for
"hidden" - in WSFTP you put "-a" (no quote marks) in the field below the
"MkDir" button and click on "Refresh". Then you can delete the file.

Any idea how this is done with CuteFTP?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,744
Messages
2,569,484
Members
44,903
Latest member
orderPeak8CBDGummies

Latest Threads

Top