 | | Re: Brickshelf suggestions (was: problems?)
|
|
(...) Don't you wish all software development was this efficient? It's even written in C. Kids, don't try this at home :) BTW, you are using Mozilla 1.1a right? Besides being a far superior browser to IE or NS it has a fortuitous bug where it (...) (22 years ago, 28-Jun-02, to lugnet.publish)
|
| |
| | Re: Brickshelf suggestions (was: problems?)
|
|
(...) I'm actually using IE but I'll check out Mozilla... (22 years ago, 28-Jun-02, to lugnet.publish)
|
| |
| | Re: Brickshelf suggestions (was: problems?)
|
|
(...) unless there's an explicit header saying the cgi has expired (which i didn't check), I say mozilla is doing the Right Thing, while IE and NS don't. A GET CGI is supposed to give the same output when it's parameters are the same, so browsers (...) (22 years ago, 28-Jun-02, to lugnet.publish)
|
| |
| | Re: Brickshelf suggestions (was: problems?)
|
|
(...) I use IE, and was quite surprised when that happened to me the first time (checking a folder and going back, just to find that another random folder appeared rather than the one I was exploring). Since then, I just open the questionable (...) (22 years ago, 28-Jun-02, to lugnet.publish)
|
| |
| | Re: Brickshelf suggestions (was: problems?)
|
|
(...) Yes. A GET CGI is supposed to give the same output when it's (...) Where does it say that a GET request always returns the same content? a GET for a dynamic page is no different than a GET for a "static" page that might change at some point. (...) (22 years ago, 28-Jun-02, to lugnet.publish)
|
| |
| | Re: Brickshelf suggestions (was: problems?)
|
|
(...) wait - am I completely confused here? I thought we wanted the cgi output to NOT expire? so that "back" will show you the same page? (...) hmmm... : 13.9 Side Effects of GET and HEAD Unless the origin server explicitly prohibits the caching of (...) (22 years ago, 28-Jun-02, to lugnet.publish)
|
