What would be even better is to just write the code right in the first place
so that no error ever happens. (I tried that. I came close.)
People make mistakes. Server software should do something reasonable. The
problem with just closing the connection is:
- the user will get connection
Yes. I am arguing that the server should always return a 500 if it
reaches
the end of a connection with no other results. I don't know the
technical
feasibility of this but it does not seem like correct behavior to return
nothing to the user.
I think the problem is that a filter can
Maybe there needs to be a flag in ns_write and friends to indicate
that something has been written to the connection. If not, send
out a 500 before closing the connection.
To me, this seems like a general error condition not specific to
filters. I imagine (but don't know for a fact) that there
Perhaps ns_atclose might fulfill some of your needs.
Build a preauth filter with a ns_atclose myproc statement in it and myproc
will be executed after everything else just before connection close.
On Monday 07 January 2002 11:14 am, you wrote:
On 2002.01.07, Jim Wilcoxson [EMAIL PROTECTED]
On 2002.01.07, David Walker [EMAIL PROTECTED] wrote:
Perhaps ns_atclose might fulfill some of your needs.
Build a preauth filter with a ns_atclose myproc statement in it and myproc
will be executed after everything else just before connection close.
Registering a script with ns_atclose won't
hmm. Under Linux I issued a ns_write command from a procedure called by
ns_atclose and the output was appended to the previous ns_write output and
displayed in my browser.
The docs don't actually specify whether it should take place before or after
the connection close.
On Monday 07 January
Totally agree. In fact, I think there may be other cases where AS 3.4
doesn't log Bad Request errors that are internally generated by AS. I
have had users do screen shots of Bad Request, yet I can't find them
in my logs. Could be stupidity on my part...dunno yet.
Jim
I can confirm that
On 2002.01.07, David Walker [EMAIL PROTECTED] wrote:
hmm. Under Linux I issued a ns_write command from a procedure called by
ns_atclose and the output was appended to the previous ns_write output and
displayed in my browser.
The docs don't actually specify whether it should take place before
] Critical filter failed
On 2002.01.07, Jim Wilcoxson [EMAIL PROTECTED] wrote:
Maybe there needs to be a flag in ns_write and friends to indicate
that something has been written to the connection. If not, send
out a 500 before closing the connection.
Strangely, while I was implementing some
On 2002.01.07, Dave Siktberg [EMAIL PROTECTED] wrote:
You could use such a feature to force the order of trace filters.
Perhaps that would address your need.
I already said that trace filters aren't what I need. Trace
filters are executed too late. Unless I'm wrong. My testing
a while back
David Walker wrote:
When the error below appears wouldn't the proper response be a 500 server
error? The 3.4 way of handling this is to return nothing.
Error: tclop: invalid return code from filter proc 'Critical filter
sec_read_security_info failed.': must be filter_ok, filter_return, or
11 matches
Mail list logo
