file name not logged w/ custom 404 error script

Thanks David,

Post processing is really not an option in this case.

Is it possible for this conversation to contine by email,
or is that not done? (This is my first time doing
whatever this is I'm doing.) I tried emailing
someone.RemoveThis@online.microsoft.com but it bounced. If your
willing please send me your microsoft.com email address
and I'll give you some more details of my problem.

Otherwise thank you for help up to this point,

Jeff Wilson


 >-----Original Message-----
 >This is a post processing task. I wouldn't try to change
the log file at
 >all.
 >
 >Instead, I suggest you use LogParser to preprocess the
log file to
 >re-arrange such entries around (i.e. it's possible to use
LogParser to
 >extract the original URL of a given 404 page and put it
back to the
 >cs-uri-stem column ).
 >
 >Then, you use your log file analyzer.
 >
 >The above would be a far easier solution than you
attempting to tackle an
 >ISAPI Filter to do something similar. Namely, you
probably do not know C,
 >and a correct ISAPI Filter is non-trivial to write.
Meanwhile, LogParser is
 >very easy to wield for such processing tasks.
 >
 >I cannot seem to find a pure Log Parser 2.1 download link.
 >- IIS Resource Kit Tools (contains Log Parser 2.1, which
you can extract
 >with "iis60rkt.exe /V/a" and then individually installed)
 >http://www.microsoft.com/downloads/details.aspx?
displaylang=en&familyid=56fc92ee-a71a-4c73-b628-
ade629c89499
 >- LogParser 2.0
 >http://www.microsoft.com/downloads/details.aspx?
displaylang=en&familyid=8cde4028-e247-45be-bab9-
ac851fc166a4
 >
 >--
 >//David
 >IIS
 >This posting is provided "AS IS" with no warranties, and
confers no rights.
 >//
 >"Jeff Wilson" <wilson.RemoveThis@silcom.com> wrote in message
 >news:01de01c36f53$6e0f21c0$a601280a@phx.gbl...
 >Hello,
 >
 >I have created a custom 404 error page which is an ASP
 >script. The script can determine the requested page (by
 >looking at request.querystring) and then process the
 >request as intended.
 >
 >However when I look in the web log file, I see the name of
 >the 404 error script rather than the name of the requested
 >file. I want the requested file stem to be shown in the
 >log file like before the custom 404 script.
 >
 >(I do see the requested file is in the query string, but
 >my log file analyser looks at the cs-uri-stem.)
 >
 >If it's not possible to have the requested file logged as
 >usual, then could I use a simple issapi filter or
 >something to perform the same function - and if so could
 >someone point me to a reference on this subject? (I am a
 >medium level Visual Basic programmer.)
 >
 >Thank you very much to anyone that will help me,
 >
 >Jeff Wilson
 >
 >
 >.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: file name not logged w/ custom 404 error script 

I don't believe there's a way to work around the default behavior. If you
want cs-uri-stem to contain the "not-found" file, why don't you just leave
it?

What result are you trying to achieve?

Mike

"Jeff Wilson" <wilson.DeleteThis@silcom.com> wrote in message
news:01de01c36f53$6e0f21c0$a601280a@phx.gbl...
 > Hello,
 >
 > I have created a custom 404 error page which is an ASP
 > script. The script can determine the requested page (by
 > looking at request.querystring) and then process the
 > request as intended.
 >
 > However when I look in the web log file, I see the name of
 > the 404 error script rather than the name of the requested
 > file. I want the requested file stem to be shown in the
 > log file like before the custom 404 script.
 >
 > (I do see the requested file is in the query string, but
 > my log file analyser looks at the cs-uri-stem.)
 >
 > If it's not possible to have the requested file logged as
 > usual, then could I use a simple issapi filter or
 > something to perform the same function - and if so could
 > someone point me to a reference on this subject? (I am a
 > medium level Visual Basic programmer.)
 >
 > Thank you very much to anyone that will help me,
 >
 > Jeff Wilson
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: file name not logged w/ custom 404 error script 

Well, my client wants smarter 404 error handling which
includes some processing that has to be done on the server
side. He also wants to contine using his existing log
file analyzer to record 404 errors.

If I can't get it to work with a custom 404 error script
then I may have to instal a Cold Fusion server which does
record the requested file in the logs - even when a custom
404 error script is used.

Jeff


 >-----Original Message-----
 >I don't believe there's a way to work around the default
behavior. If you
 >want cs-uri-stem to contain the "not-found" file, why
don't you just leave
 >it?
 >
 >What result are you trying to achieve?
 >
 >Mike
 >
 >"Jeff Wilson" <wilson.RemoveThis@silcom.com> wrote in message
 >news:01de01c36f53$6e0f21c0$a601280a@phx.gbl...
  >> Hello,
  >>
  >> I have created a custom 404 error page which is an ASP
  >> script. The script can determine the requested page (by
  >> looking at request.querystring) and then process the
  >> request as intended.
  >>
  >> However when I look in the web log file, I see the name
of
  >> the 404 error script rather than the name of the
requested
  >> file. I want the requested file stem to be shown in the
  >> log file like before the custom 404 script.
  >>
  >> (I do see the requested file is in the query string, but
  >> my log file analyser looks at the cs-uri-stem.)
  >>
  >> If it's not possible to have the requested file logged
as
  >> usual, then could I use a simple issapi filter or
  >> something to perform the same function - and if so could
  >> someone point me to a reference on this subject? (I am
a
  >> medium level Visual Basic programmer.)
  >>
  >> Thank you very much to anyone that will help me,
  >>
  >> Jeff Wilson
  >>
 >
 >
 >.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: file name not logged w/ custom 404 error script 

I don't believe there's a way to work around the default behavior. If you
want cs-uri-stem to contain the "not-found" file, why don't you just leave
it?

What result are you trying to achieve?

Mike

"Jeff Wilson" <wilson DeleteThis @silcom.com> wrote in message
news:01de01c36f53$6e0f21c0$a601280a@phx.gbl...
 > Hello,
 >
 > I have created a custom 404 error page which is an ASP
 > script. The script can determine the requested page (by
 > looking at request.querystring) and then process the
 > request as intended.
 >
 > However when I look in the web log file, I see the name of
 > the 404 error script rather than the name of the requested
 > file. I want the requested file stem to be shown in the
 > log file like before the custom 404 script.
 >
 > (I do see the requested file is in the query string, but
 > my log file analyser looks at the cs-uri-stem.)
 >
 > If it's not possible to have the requested file logged as
 > usual, then could I use a simple issapi filter or
 > something to perform the same function - and if so could
 > someone point me to a reference on this subject? (I am a
 > medium level Visual Basic programmer.)
 >
 > Thank you very much to anyone that will help me,
 >
 > Jeff Wilson
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: file name not logged w/ custom 404 error script 

Why is Post processing not an option? Is it impossible for your client to
run a single pre-cooked commandline from you to do this prior to them
running their log analysis package? Because that's all it'd take.

Note the consequences of the other two solutions you suggested. Running
Cold Fusion simply to change the log file name is like using a sledgehammer
for the vibrations it can cause 10 feet away -- it has way too big an impact
on your system stability, security, and function simply for a logging
change. Writing a custom ISAPI Filter can get the job done (how do you
think Cold Fusion accomplishes this?), but you'd need to learn C and ISAPI
Filter just to do this.

So, out of the three choices, I think Post processing is the least impactful
to the server and to you, and it's just running a single pre-cooked
commandline prior to running the log analysis package.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Jeff Wilson" <wilson.RemoveThis@silcom.com> wrote in message
news:00b601c36f7d$b3135690$a001280a@phx.gbl...
Thanks David,

Post processing is really not an option in this case.

Is it possible for this conversation to contine by email,
or is that not done? (This is my first time doing
whatever this is I'm doing.) I tried emailing
someone.RemoveThis@online.microsoft.com but it bounced. If your
willing please send me your microsoft.com email address
and I'll give you some more details of my problem.

Otherwise thank you for help up to this point,

Jeff Wilson


 >-----Original Message-----
 >This is a post processing task. I wouldn't try to change
the log file at
 >all.
 >
 >Instead, I suggest you use LogParser to preprocess the
log file to
 >re-arrange such entries around (i.e. it's possible to use
LogParser to
 >extract the original URL of a given 404 page and put it
back to the
 >cs-uri-stem column ).
 >
 >Then, you use your log file analyzer.
 >
 >The above would be a far easier solution than you
attempting to tackle an
 >ISAPI Filter to do something similar. Namely, you
probably do not know C,
 >and a correct ISAPI Filter is non-trivial to write.
Meanwhile, LogParser is
 >very easy to wield for such processing tasks.
 >
 >I cannot seem to find a pure Log Parser 2.1 download link.
 >- IIS Resource Kit Tools (contains Log Parser 2.1, which
you can extract
 >with "iis60rkt.exe /V/a" and then individually installed)
 >http://www.microsoft.com/downloads/details.aspx?
displaylang=en&familyid=56fc92ee-a71a-4c73-b628-
ade629c89499
 >- LogParser 2.0
 >http://www.microsoft.com/downloads/details.aspx?
displaylang=en&familyid=8cde4028-e247-45be-bab9-
ac851fc166a4
 >
 >--
 >//David
 >IIS
 >This posting is provided "AS IS" with no warranties, and
confers no rights.
 >//
 >"Jeff Wilson" <wilson.RemoveThis@silcom.com> wrote in message
 >news:01de01c36f53$6e0f21c0$a601280a@phx.gbl...
 >Hello,
 >
 >I have created a custom 404 error page which is an ASP
 >script. The script can determine the requested page (by
 >looking at request.querystring) and then process the
 >request as intended.
 >
 >However when I look in the web log file, I see the name of
 >the 404 error script rather than the name of the requested
 >file. I want the requested file stem to be shown in the
 >log file like before the custom 404 script.
 >
 >(I do see the requested file is in the query string, but
 >my log file analyser looks at the cs-uri-stem.)
 >
 >If it's not possible to have the requested file logged as
 >usual, then could I use a simple issapi filter or
 >something to perform the same function - and if so could
 >someone point me to a reference on this subject? (I am a
 >medium level Visual Basic programmer.)
 >
 >Thank you very much to anyone that will help me,
 >
 >Jeff Wilson
 >
 >
 >.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: file name not logged w/ custom 404 error script