network profile
| bio | website | bellenett.no |
|---|---|---|
| location | Trondheim, Norway | |
| age | ||
| visits | member for | 1 year |
| seen | Jul 9 '12 at 17:19 | |
| stats | profile views | 1 |
I am a designer / coder working to create areas of interaction between website owners and their visitors, be it technical, in the universe of content or as human relations. My mantra might be "What do you want your site(s!) to do for you today?" signifying the idea that an ideal site is focused in a way that makes it clear why you made it. This offers the visitor an opportunity to enhance his or her life, or leave. Maybe to another site of yours?
My task is to make the site become real - drawing, coding, consulting, measuring, redesigning, redraw, recode and so on. A website is a dynamic entity, and I'll harness its power.
|
Jan 10 |
awarded | Teacher |
|
Jun 18 |
awarded | Editor |
|
Jun 18 |
revised |
how should cache control be set in the requests Emphasis on *request* headers, which was my original meaning, and the meaning of the paragraph as a whole. |
|
Jun 18 |
comment |
how should cache control be set in the requests Thanks, I understand better your intention. I'm afraid I can't really help you better anyway, but I'd like to offer a couple of points to ponder. It is all HTTP that is considered here. Of course, you'll want HTTPS or some secure transport, so your confidential data can't be snooped on its way to the server. This will also ensure (as far as I can see) that even if it is cached, it will not be readable: Even if there might be a cache header that should prevent caching, there is no guarantee that servers comply to the spec. |
|
Jun 11 |
answered | Redirect subdomain (weblog) to new domain without access to .htaccess |
|
Jun 11 |
answered | how should cache control be set in the requests |
