I was having trouble understanding a line in my FAILURE report which indicated that there were numerous failures on references to a particular directory where I know there is an index.html file.

After extracting and trying different lines from my log file I finally
determined that some of these were due to failed PROPFIND requests as
in the following

   PROPFIND /humanresources/ HTTP/1.1" 405 259

where I've removed all of the non relevant info from the log entry to improve readability. In all cases the "user agent" was
reported as "Microsoft-WebDAV-MiniRedir/5.1.2600" if that makes any
difference.


I've temporarily fixed this problem using "STATUSEXCLUDE 405", but I
tend to think that its a bug to include failed PROPFINDs in the FAILURE
report. I don't run WebDAV, BTW, and all of these requests appear to be
probes from an unknown source.

I happened to find this problem while trying to resolve a problem with
FILEALIAS. I use a symbolic link "hr" to allow "/hr" references to the
"/humanresources" web site and I thought the following

  FILEALIAS REGEXP:^/(hr|$) /humanresources/

would do the trick, but I realized it wasn't working as expected when
I observed that "/humanresoucres/" was at the top of the FAILURE report,
partly because of the aforementioned PROPFINDs, but mostly because requests
like

  "GET /hr/red/2nd%20Level%20Template_files/pixel.gif HTTP/1.1" 404 247

were mapped to failed references to /humanresources/. I then changed the
FILEALIAS to match the entire path as in

  FILEALIAS REGEXP:^/hr($|\/$|\/.*$) /humanresources$1

and sure enough this fixed the problem. However, I'm wondering why I have to match the entire path when its a regexp, since ^ and $ are
available for indicating the beginning and end of the string and its
fairly common practice (in Perl at least) to use these to anchor the
pattern to a indicate a specific substring to match and replace.


If there is a good reason why allowing substring replacement isn't
feasible, making this clear in the documentation would be a help.

BTW, the regexp that is working seems overly complicated, but I was
trying to match all of

   /hr
   /hr/
   /hr/abc/def/xyz.html

and hence the alternatives. Do I really need all of these or is there
a simpler form for the regexp?

TIA.

- rick
+------------------------------------------------------------------------
|  TO UNSUBSCRIBE from this list:
|    http://lists.meer.net/mailman/listinfo/analog-help
|
|  Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
|  List archives:  http://www.analog.cx/docs/mailing.html#listarchives
+------------------------------------------------------------------------

Reply via email to