The debian-private mailing list leak, part 1. Volunteers have complained about Blackmail. Lynchings. Character assassination. Defamation. Cyberbullying. Volunteers who gave many years of their lives are picked out at random for cruel social experiments. The former DPL's girlfriend Molly de Blanc is given volunteers to experiment on for her crazy talks. These volunteers never consented to be used like lab rats. We don't either. debian-private can no longer be a safe space for the cabal. Let these monsters have nowhere to hide. Volunteers are not disposable. We stand with the victims.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debian WWW Guidelines?!

cas@taz.net.au (Craig Sanders)  wrote on 14.03.97 in <Pine.LNX.3.95q.970314110202.996c-100000@siva.taz.net.au>:

> On Thu, 13 Mar 1997, [iso-8859-1] Nicolás Lichtmaier wrote:
>
> > On Thu, 13 Mar 1997, Craig Sanders wrote:
> >
> > > it is possible to redirect to a different index page depending on
> > > whether the browser supports tables or frames or not.
> >
> >  That's very bad. You don't know who is seeing you page just by looking
> > `User-Agent:', there may be proxies in the middle.
>
> proxies shouldn't modify the User-Agent field.

I may be wrong, but I seem to recall that *all* of them do.

Also, some clients lie. MSIE has been known to masquerade as Netscape, for  
example.

User-Agent is a problematic field to base decisions on.

> > And using includes and html would force caches to not caching our
> > pages...
>
> yes. that is a big problem with includes. however, there are ways around
> it.  e.g. set the Last-Modified: header to be the same as the newest
> included file... the same tricks which can be used to make cgi output
> cache-friendly.

Only that makes it user-unfriendly, as you get whatever was appropriate  
for the user who caused it to be cached.

I think the only way to do this that really works with caches, would be to  
have the first URL do a redirect according to client capabilities, an from  
then on work with different URLs. This also means you only have to do this  
once.

And the *best* way is probably not to do it at all. Write the pages such  
that they work with the current Debian Lynx version, and still look nice  
in Netscape and MSIE, and forget about stuff that doesn't work in this  
context.

MfG Kai