1. 27 Nov, 1999 2 commits
  2. 26 Nov, 1999 3 commits
  3. 25 Nov, 1999 1 commit
  4. 24 Nov, 1999 4 commits
    • Martin Kraemer's avatar
      This patch fixes the some of the bogosity in regular expressions · 186dc5e9
      Martin Kraemer authored
      on EBCDIC based machines: a character range [a-z] would match much more
      than only the islower() characters because in the EBCDIC charset there
      are "holes in the contiguity" between a-i, j-r and s-z.
      
      This patch fixes [<lowercase>-<lowercase>] and [<uppercase>-<uppercase>]
      ranges by only regarding alphabetic characters between the lower and
      upper bound. (Any other range definition remains unchanged.)
      
      
      git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@84154 13f79535-47bb-0310-9956-ffa450edef68
      186dc5e9
    • dgaudet's avatar
      no comment on the rest of this... but this is for debugging, and i don't · 2838ec78
      dgaudet authored
      want a debugging tool losing information for me for the sake of "looking
      good".
      
      
      git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@84153 13f79535-47bb-0310-9956-ffa450edef68
      2838ec78
    • Martin Kraemer's avatar
      89bdec33
    • Ralf S. Engelschall's avatar
      I know we don't want to see any "fancy" things in our printenv (as · e9b3867c
      Ralf S. Engelschall authored
      they were already posted by various users over the last years), but
      every time I need to use a little CGI script for testing purposes I get
      annoyed by this really too weak printenv script. Sure, tables and other
      stuff should be not our business, but at least the script should be a
      little bit more robust and useful.
      
      What I disliked most is that I usually have great problems to easily find a
      variable (because the output is not sorted) and that various environment
      values totally destroy the optical view on the table as a whole (mainly too
      large values in $PATH and the nasty contents of SERVER_SIGNATURE). So here is
      my minimal change to at least fix these problems without introducing fancy or
      insecure stuff.  Nevertheless feel free to back it out if you definitely
      dislike any changes to printenv at all.
      
      My changes are:
      
      1. add a comment line to make it clear to the user that this is more or less
         just a silly _demo_ script (for those who don't have Perl as their
         secondary language beside their native language)
      
      2. use content type text/plain instead of text/html to easily avoid printing
         problems with variables like SERVER_SIGNATURE which contains HTML
         code. This way we have to add extra escaping steps and the script
         remains small.
      
      3. sort the variables lexicographically in the output!
      
      4. make sure very large lines (usually from $PATH) do not destroy the
         total optical view on the table by cutting values and replacing
         the missing stuff with "[...]".
      
      5. surround values with quotes to allow one to better recognize newlines (as
         in SERVER_SIGNATURE) and whitespaces and also print newlines
         as \n and " as \" for a more Shell- and C-style syntax.
      
      
      git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@84150 13f79535-47bb-0310-9956-ffa450edef68
      e9b3867c
  5. 23 Nov, 1999 2 commits
  6. 22 Nov, 1999 1 commit
  7. 20 Nov, 1999 1 commit
  8. 18 Nov, 1999 2 commits
  9. 17 Nov, 1999 2 commits
  10. 16 Nov, 1999 1 commit
  11. 14 Nov, 1999 1 commit
  12. 09 Nov, 1999 1 commit
  13. 05 Nov, 1999 2 commits
  14. 04 Nov, 1999 2 commits
  15. 02 Nov, 1999 1 commit
  16. 01 Nov, 1999 2 commits
    • dgaudet's avatar
      i asked a friend who does interface design to comment on the "it worked" · 450c9faa
      dgaudet authored
      page.  i liked what he had to say.
      
      > From: James Home <jim@vagabondage.com>
      >
      > reading over the page, it appears that the primary audience for the
      > page is the person who's installing Apache. this doesn't really make
      > sense though; the only information it's necessary to convey to that
      > person is that the server is working, and the simple presence of the
      > page does that.  sure, there are the links to the Apache homepage and
      > to documentation, but those don't require much prominence; if someone
      > is looking for them, they're easy to find.
      >
      > I'd say that the primary audience for the *information* on the page
      > is the poor befuddled user who doesn't know an Apache helicopter from
      > an Apache web server and wants to know what happened to the website
      > they've spent weeks working on.
      >
      > so how is a user like that going to experience the page?
      >
      > - a logo that they don't recognize at the bottom of the page
      > apparently claiming responsibility for it;
      >
      > - some confusing "It Worked!" message at the top of the page;
      >
      > - a somewhat threatening and vague message that, despite the fact
      > that this page is all about this mysterious software called Apache
      > (note that it isn't explained that Apache is web server software
      > until the very last line of small text), Apache isn't responsible for
      > the site, and I should "contact the administrator of the site
      > involved" (of course, if I was an end user who didn't understand how
      > web servers work, I would assume *I* was the administrator of my
      > site, leaving only this mysterious organization to contact).
      >
      > - clicking on the most prominent link takes me to another page that
      > doesn't specifically mention web servers.  there's a contact link
      > though, which takes me to the page with the email address and Sally's
      > phone number.
      >
      > I did a quick mockup to demonstrate how I think this might work better:
      >
      > http://www.vagabondage.com/~jim/apache/worked2.html
      
      Submitted by:	James Home <jim@vagabondage.com>
      
      
      git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@84086 13f79535-47bb-0310-9956-ffa450edef68
      450c9faa
    • Tony Finch's avatar
      I had to chase too many links to find the content negotiation docs · 2b438087
      Tony Finch authored
      just now so this'll make it easier to get to.
      
      
      git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@84085 13f79535-47bb-0310-9956-ffa450edef68
      2b438087
  17. 29 Oct, 1999 2 commits
  18. 28 Oct, 1999 3 commits
  19. 27 Oct, 1999 7 commits