[DAS2] mtg topics for Nov 28

[Helt,Gregg]

Actually I think by default the java networking library that IGB uses
follows most redirections automatically without IGB having to worry
about it.  I'm not familiar with what different forms of redirection
might do to the status codes, but I expect that as long as the
redirection is successful the code IGB would actually see would be 200
OK.

IGB does have a ways to go to properly respond to all possible HTTP
status codes though...

	gregg

> -----Original Message-----
> From: das2-bounces at portal.open-bio.org
[mailto:das2-bounces at portal.open-
> bio.org] On Behalf Of Ed Erwin
> Sent: Tuesday, November 29, 2005 4:34 PM
> To: Andrew Dalke
> Cc: DAS/2
> Subject: Re: [DAS2] mtg topics for Nov 28
> 
> 
> >> I'm currently using the "proxy" form of redirect, which seems to
keep
> >> the status code intact.  Earlier I was using the "redirect" form of
> >> redirect, which may change the status code to 302.
> >
> >
> > I don't understand how the old one would be a problem in the
> > web clients I'm familiar with.  It should be:
> >
> >   send request to server
> >       get 302 "moved temporarily" response along with new URL
> >   repeat until no redirect or reached max redirect limit
> >   request new URL
> >       get headers/payload back
> 
> Unlike modern web browsers, IGB isn't smart enough to do that.  Maybe
> someday it will need to be, but it isn't there yet.
> 
> 
> _______________________________________________
> DAS2 mailing list
> DAS2 at portal.open-bio.org
> http://portal.open-bio.org/mailman/listinfo/das2