[Zope3-dev] RFC: Use 303 redirects by default

[Jim Fulton]

We may be in luck. See my comment on the Wiki page.

It maybe that Browsers that don't recognize 303 are HTTP/1.0. For
HTTP/1.0 browsers, we should continue to use 302.  That prevents
breakage for Netscape 4.  I wonder if there are any browsers that support
HTTP/1.1 and not status 303. Maybe there aren't any.

Jim

"Phillip J. Eby" wrote:
> 
> At 07:25 PM 6/11/02 +0100, Steve Alexander wrote:
> >See:
> >
> >http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/Use303Redi
> rectsByDefault
> >
> >Comments welcome.
> >
> 
> I don't get this at all.  It looks like this change will break for Netscape
> 4.x, with no compensating benefit.  Why do it?  Do we *want* manual
> verification of redirected POST?  Every existing usage that I know of in
> Zope (and in my apps) of redirect is intended to NOT have a manual
> verification.  Since the "de facto" interpretation of 302 works correctly -
> for what we *want* it to do - why change to another code that doesn't work
> with browsers "in the field"?  Do we believe that some future browser
> versions will implement 302 correctly, and thus break our current
> functionality?
> 
> I'm confused.
> 
> _______________________________________________
> Zope3-dev mailing list
> Zope3-dev@zope.org
> http://lists.zope.org/mailman/listinfo/zope3-dev

--
Jim Fulton           mailto:jim@zope.com       Python Powered!        
CTO                  (888) 344-4332            http://www.python.org  
Zope Corporation     http://www.zope.com       http://www.zope.org