Re: expire headers in mac305b11

This WebDNA talk-list message is from

1999

It keeps the original formatting. numero = 25108
interpreted = N
texte = >We noticed that some people visiting the site were unable to use their back>button at all on some of our pages. They got the data expired from cache>message. Reverting back to v3.0.4 made the problem go away.What browser was being used? Was it a form method=POST?We're more than willing to rethink the MIME header issue. What's going on here is that we're *more* compliant with RFC standards for CGIs now, and in 3.0.4 it was just accidental that we didn't put out the proper headers. So now people are depending on this behavior.What would you think about a new special WebDNA tag that was responsible for shooting out those headers, so by default we don't send them unless you explicitly put the tag in? The whole reason for those headers was to get around the nasty IE problem where it would *always* cache everything.Grant Hulbert , Director of R & D **********************************Smith Micro, Internet Solutions Div | Formerly, Pacific Coast Software16855 West Bernardo Drive | -------------------------Suite 380 | eCommerce (WebCatalog)San Diego, CA 92127 | Software & Site Development858.675.1106 | http://www.smithmicro.com858.675.0372 (fax) **********************************#############################################################This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to To switch to the INDEX mode, E-mail to Send administrative queries to Associated Messages, from the most recent to the oldest:

Re: expire headers in mac305b11 (Gary Richter 1999)
Re: expire headers in mac305b11 (Joseph D'Andrea 1999)
Re: expire headers in mac305b11 (Grant Hulbert 1999)
expire headers in mac305b11 (Joseph D'Andrea 1999)

>We noticed that some people visiting the site were unable to use their back>button at all on some of our pages. They got the data expired from cache>message. Reverting back to v3.0.4 made the problem go away.What browser was being used? Was it a form method=POST?We're more than willing to rethink the MIME header issue. What's going on here is that we're *more* compliant with RFC standards for CGIs now, and in 3.0.4 it was just accidental that we didn't put out the proper headers. So now people are depending on this behavior.What would you think about a new special WebDNA tag that was responsible for shooting out those headers, so by default we don't send them unless you explicitly put the tag in? The whole reason for those headers was to get around the nasty IE problem where it would *always* cache everything.Grant Hulbert , Director of R & D **********************************Smith Micro, Internet Solutions Div | Formerly, Pacific Coast Software16855 West Bernardo Drive | -------------------------Suite 380 | eCommerce (WebCatalog)San Diego, CA 92127 | Software & Site Development858.675.1106 | http://www.smithmicro.com858.675.0372 (fax) **********************************#############################################################This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to To switch to the INDEX mode, E-mail to Send administrative queries to Grant Hulbert

DOWNLOAD WEBDNA NOW!

Re: expire headers in mac305b11

1999

Top Articles:

Related Readings: