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.)
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
feasibi
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
Hmmm.
I could use an example - the current system works fine with base64, but
I will be writing v2 (incompatible with v1, of course :) and could use
multipart...
--
WK
Mike Hoegeman wrote:
> if you use mime multi-part posts to upload files, you should not have
> the problem above (if i remembe
Jim Wilcoxson wrote:
>
> Do this:
>
> ns_section "ns/server/${servername}"
> ns_param maxpost 131072;# Max bytes on a POST
>
> Jim
>
> >
> > Hello.
> >
> > I've hit a major problem.
> >
> > I want to send base64 encoded files through HTTP - the files are from
> > 100 to 10 bytes.
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
filter_break
Yeap, grepped it a minute after posting this one.
Mentioned in doc/config.txt or something :)
But thanks anyway
Jim Wilcoxson wrote:
> Do this:
>
> ns_section "ns/server/${servername}"
> ns_param maxpost 131072;# Max bytes on a POST
>
> Jim
>
>
>>Hello.
>>
>>I've hit a major prob
Do this:
ns_section "ns/server/${servername}"
ns_param maxpost 131072;# Max bytes on a POST
Jim
>
> Hello.
>
> I've hit a major problem.
>
> I want to send base64 encoded files through HTTP - the files are from
> 100 to 10 bytes. When uploading a 80k file, I occured this probl
Hello.
I've hit a major problem.
I want to send base64 encoded files through HTTP - the files are from
100 to 10 bytes. When uploading a 80k file, I occured this problem:
[06/Jan/2002:20:20:22][1030.19474][-conn1-] Warning: conn: post size
123377 exceeds maxpost limit of 65536
The files ar
Are you saying that if you add a "." to the end of the url that it returns a
file it shouldn't?
I haven't checked it out but if it is a problem you can create a filter that
matches "*." and returns a not found message.
On Saturday 05 January 2002 02:38 pm, you wrote:
> I found possible bug, just
On 2002.01.05, Tamer Sahin <[EMAIL PROTECTED]> wrote:
> I found possible bug, just get url http://host/nstelemetry.adp.
> then download password protected file.
>
> I have test Windows version AOLServer 3.4.2
Yet another reason why dropping Windows support in AOLserver 4
makes sense.
-- Dossy
10 matches
Mail list logo