We're serving up our feeds with auth and ssl. Julian Reschke wrote: > James M Snell wrote: >> Hey, I never said I *wasn't* abusing the headers ;-) Can you say >> serendipitous hack? ;-) >> >> What we're doing may not be 100% per spec, but it doesn't seem to cause >> any problems either... other than some nominal wierdness in feed readers >> that support conditional gets but don't keep a feed history (like >> Firefox Live Bookmarks). In other words, assuming that some offenses >> are more egregious than others, this is kind of like a rolling stop >> through a four way intersection in the middle of the desert when there >> aren't any other vehicles around. > > I would expect to see problems as soon as cacheing HTTP proxies are in > the request path. > > Best regards, Julian >
- Re: Yet another APP client James M Snell
- Re: Yet another APP client Toru Marumoto
- Re: Yet another APP client Thomas Broyer
- Re: Yet another APP client Toru Marumoto
- Re: Yet another APP client Thomas Broyer
- Re: Yet another APP client Toru Marumoto
- Re: Yet another APP client James M Snell
- Re: Yet another APP client Thomas Broyer
- Re: Yet another APP client James M Snell
- Re: Yet another APP client Julian Reschke
- Re: Yet another APP client James M Snell
- Re: Yet another APP client Walter Underwood
- Re: Yet another APP client James M Snell
- Re: Yet another APP client Thomas Broyer
- Re: Yet another APP client Julian Reschke
- Re: Yet another APP client James M Snell
- Re: Yet another APP client Tim Bray
- Re: Yet another APP client James M Snell
- Re: Yet another APP client David Sklar
- Re: Yet another APP client Kyle Marvin
- Re: Yet another APP client Tim Bray
