[OpenAFS] OpenAFS Web page...

[Jeffrey Hutzelman]

On Friday, July 15, 2005 01:45:59 AM -0400 Rodney M Dyer <rmdyer@uncc.edu> 
wrote:

> My job is kind of stressful because I'm working against the tsunami of
> Novell on our campus.  Trying to prove that AFS is worth its mettle isn't
> easy when the web site contains problems.  The upper management doesn't
> like inconsistency.

Mine is stressful because I need to get a new platform port out by fall and 
have about a months worth of work to do by two weeks ago in order to get it 
to beta in time for me to leave town on Monday.  Next? :-)


> As for the other problems, I don't know.  Claiming that just because a
> line feed doesn't appear on browsers besides IE,

I didn't say that.  I said I couldn't reproduce it, and that you didn't 
tell me what your browser was, and that I didn't have time to test every 
possible browser.  What I do instead is keep to a relatively small and 
widely-implemented subset of a long-established standard, which is, after 
all, a big part of what standards are for.

Now, if you want to tell me what browser you have, and describe the problem 
in more detail, _maybe_ I can come up with a fix that won't screw it up for 
someone else.  Sending a patch isn't required, but wouldn't hurt, either. 
:-)



 and that "i'm being
> protected"

You'll note I put that in quotes; I was mocking the browser behavior. 
Again, I can't reproduce the problem, and you didn't tell me what your 
browser is.  The web server is sending the correct type and encoding 
information, which means a browser that recognizes those types is able to 
automatically decompress the file and can determine what applications might 
be appropriate to open it with.

As I said, probably what's going on here is that your browser is trying to 
be "helpful" by giving the file an extension based on what it thinks its 
type is, instead of using the name provided by the server.  If this is the 
case, there is _nothing I can do_ about it.  Feel free to try to find some 
other site where the same thing works for you, and tell me what's 
different.  But given that 99.99999% of the people who download the source 
tarballs are not running Windows, I'm not going to cause the web server to 
misidentify their type or encoding in order to placate Windows.