Skip to content
GitLab
  1. 03 Mar, 1998 12 commits
  3. 02 Mar, 1998 10 commits
  5. 01 Mar, 1998 7 commits
  7. 28 Feb, 1998 6 commits
  9. 27 Feb, 1998 5 commits
    • Martin Kraemer's avatar
      Dean, this 'make depend' stuff was a great job · 7e7c6e4a
      Martin Kraemer authored 
      
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@80339 13f79535-47bb-0310-9956-ffa450edef68
      7e7c6e4a
    • Martin Kraemer's avatar
      Reflect Year-1998 reality · 7cb3ccab
      Martin Kraemer authored 
      
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@80338 13f79535-47bb-0310-9956-ffa450edef68
      7cb3ccab
    • Martin Kraemer's avatar
      For testing purposes, I added a new source called main/util_uri.c; · f7f3763b
      Martin Kraemer authored 
      It contains a routine parse_uri_components_regex() and friends which
tries to break an URI into its parts. These parts are stored in a new
uri_components structure within each request_rec and are therefore
available to all routines which act on a request.
Additionally, an unparse routine is supplied which re-assembles the
URI components back to an URI, optionally hiding the username:password@
part from ftp proxy requests, and other useful routines.
Within the structure, you find on a ready-for-use basis:
   scheme;     /* scheme ("http"/"ftp"/...) */
   hostinfo;   /* combined [user[:password]@]host[:port] */
   user;       /* user name, as in http://user:passwd@host:port/ */
   password;   /* password, as in http://user:passwd@host:port/ */
   hostname;   /* hostname from URI (or from Host: header) */
   port_str;   /* port string (integer representation is in "port") */
   path;       /* the request path (or "/" if only scheme://host was given) */
   query;      /* Everything after a '?' in the path, if present */
   fragment;   /* Trailing "#fragment" string, if present */
plus flags to indicate whether the strings have valid values.
This is meant to serve as the platform for *BIG* savings in
code complexity for the proxy module (and maybe the vhost logic).
NOTE: This code is enabled only if the WITH_UTIL_URI define is set;
currently this is not enabled by default.  [Martin Kraemer]

Reviewed by: Dean Gaudet (on a previous occasion)


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@80337 13f79535-47bb-0310-9956-ffa450edef68
      f7f3763b
    • Ralf S. Engelschall's avatar
      Document the now achieved equality of possible meta-construct · a328a45c
      Ralf S. Engelschall authored 
      expansions in mod_rewrite rulesets.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@80336 13f79535-47bb-0310-9956-ffa450edef68
      a328a45c
    • Ralf S. Engelschall's avatar
      It's unbelievable, it's unbelievable... · 4916a47f
      Ralf S. Engelschall authored 
      We have three locations where one can construct a string in rewriting rules by
expanding $N, %N, %{NAME} and ${map:key}:

  - RewriteCond <Location-1>  ...
  - RewriteRule ...           <Location-2> ...
  - RewriteRule ...           ...          [..,E=NAME:<Location-3>,...]

And just after I've added exact comments of what we expand in each location, I
discovered that they are expanded totally inconsequent. For <Location-3> the
%{NAME} and ${map:key} constructs were not expanded (ok, perhaps not really a
%major drawback) and for <Location-1> the ${map:key} construct was not
%expanded while for <Location-2> all are expanded. At least the missing
${map:key} expansion for <Location-1> is horrible because this way we
unnesessarily restricted the usefulness of RewriteCond dramatically.

Perhaps I should add more source comments to mod_rewrite.c
to discover that it then can even can cook a cake now.... ;-)


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@80335 13f79535-47bb-0310-9956-ffa450edef68
      4916a47f