an error that does not happen through 500-100.asp

[reo]

if I put in a pagina asp the instruction:
server.scriptti meout=1
the page indeed expires immediately,
but the error that produces does not get to happen through 500-100.asp some
solution,
since to treat the errors I make it from 500-100.asp
thank you very much

[Patrice]

What if you try a higher number ? AFAIK our timeouts are processed but of
course we have a bigger value than that.

Patrice

--

"reo" <re*@cetel.es > a écrit dans le message de
news:uu******** ******@TK2MSFTN GP11.phx.gbl...

if I put in a pagina asp the instruction:
server.scriptti meout=1
the page indeed expires immediately,
but the error that produces does not get to happen through 500-100.asp some solution,
since to treat the errors I make it from 500-100.asp
thank you very much

[Bob Barrows [MVP]]

No, you don't understand: he's using the small number to deliberately force
the timeout so he can figure out how to gracefully handle timeouts if they
occur after setting the value to a more normal number.

Unfortunately, I don't knowthe answer. I typically concentrate on making
sure timeouts don't happen avoiding operations that should not be done in
ASP.

Bob Barrows

Patrice wrote:

What if you try a higher number ? AFAIK our timeouts are processed
but of course we have a bigger value than that.

Patrice
"reo" <re*@cetel.es > a écrit dans le message de
news:uu******** ******@TK2MSFTN GP11.phx.gbl...

if I put in a pagina asp the instruction:
server.scriptti meout=1
the page indeed expires immediately,
but the error that produces does not get to happen through
500-100.asp some solution,
since to treat the errors I make it from 500-100.asp
thank you very much

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

[Patrice]

I just wanted to know what would happen with a more reaslistic number (let's
say 30 instead of just 1 s).

The reason for this is that it works here so I would think that either the
500-100.asp page is not configured properly or that for some reason such an
irrealistic number causes some kind of strange behavior (for example what if
the timeout is lower than the time needed for the 500-100.asp page ???).

I would still recommand :
- what if ther page creates a non timeout error (such a computing 2/0) and
chekc that the 500-100 page is called
- if yes, trying with a realistic number for the timeout

Patrice

--

"Bob Barrows [MVP]" <re******@NOyah oo.SPAMcom> a écrit dans le message de
news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..

No, you don't understand: he's using the small number to deliberately force the timeout so he can figure out how to gracefully handle timeouts if they
occur after setting the value to a more normal number.

Unfortunately, I don't knowthe answer. I typically concentrate on making
sure timeouts don't happen avoiding operations that should not be done in
ASP.

Bob Barrows

Patrice wrote:

What if you try a higher number ? AFAIK our timeouts are processed
but of course we have a bigger value than that.

Patrice
"reo" <re*@cetel.es > a écrit dans le message de
news:uu******** ******@TK2MSFTN GP11.phx.gbl...

if I put in a pagina asp the instruction:
server.scriptti meout=1
the page indeed expires immediately,
but the error that produces does not get to happen through
500-100.asp some solution,
since to treat the errors I make it from 500-100.asp
thank you very much

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

[snichol]

reo wrote:

*if I put in a pagina asp the instruction:
server.scriptti meout=1
the page indeed expires immediately,
but the error that produces does not get to happen throug
500-100.asp some
solution,
since to treat the errors I make it from 500-100.asp
thank you very much *

Does the page do a Response.Flush before this code? It is m
experience that an undocumented feature of ASP is that it will not ru
a custom error handler such as 500-100.asp after a Response.Flush
-
snicho
-----------------------------------------------------------------------
Posted via http://www.codecomments.co
-----------------------------------------------------------------------