> Thanks for the reply Boris. Changing to 'Trap all errors' (assuming
> that's what you meant) does return to the browser. That's better except
> that it returns a code 500 and says there is an 'Internal server error'
> which isn't what the user will expect to see from a missing file. It
> makes it look like there is a bug in the web server, and perhaps there
> really is.
>
> Again, thanks. :-)
>
> -Carl Gundel
>
http://www.runbasic.com>
>> What happens if you configure the server to suppress errors?
>>
>> Cheers!
>>
>> -Boris
>
>>
>> I realize this isn't exactly a Seaside question, but I'm using
>> Seaside+VisualWave, so perhaps it's right to ask this question here.
>>
>> I'm puzzled why VisualWave throws an exception and opens a walkback when
>> I
>> try to access a file resource that doesn't exist. Why doesn't it return
>> a
>> 404 to the browser?
>>
>> \Unhandled exception: ERROR_FILE_NOT_FOUND
>> ("c:\vw7.4.1\bin\win\ribbit.png")
>> FileErrorHolder class(OSErrorHolder class)>>reportProceedingOn:
>> FileErrorHolder(OSErrorHolder)>>reportErrorProceeding
>> optimized [] in OSErrorHolder class>>initializeErrorActions
>> SystemError>>handleErrorFor:
>> FATFilename(Filename)>>isDirectory
>> VisualWave.WebSiteFile>>canServeFile
>> optimized [] in VisualWave.WebSiteFile>>handleFileRequest
>> SignalHandler>>handleDo:
>> SignalHandler>>handleDo:
>> HandlerList>>handleDo:
>> VisualWave.WebSiteFile>>handleFileRequest
>> VisualWave.WebSiteFile>>doGet
>> VisualWave.WebSiteFile(VisualWave.SingleThreadModelServlet)>>service:response:
>> VisualWave.ServletHandler>>basicEvaluate
>> optimized [] in VisualWave.WWHandler>>evaluate
>>
>> -Carl
Locked
