Roland, On the 5.5.020 and 6.0.3 Witango (Windows platform) putting code in that file works as expected. I believe you are familiar with error handler, which parses the error, creates objects and called methods, executes database actions, sends email and returns various "friendly" results to the user. All in all that aspect has been very useful for me.
If you are experiencing an issue, please submit a bug or email [email protected] with your platform, version and a copy of the error.tml file. Robert -----Original Message----- From: Roland Dumas [mailto:[email protected]] Sent: Tuesday, December 14, 2010 4:34 PM To: [email protected] Subject: Re: Witango-Talk: customizing the 404 error response what I don't get is that there is an architecture for handling errors in a custom fashion by pointing to an error file. A placeholder file is installed by default. Just if you put anything in that file, the server crashes. Is that a bug in the server, or was Bill Conlon's code somehow a wrong approach? _________________________ Roland A. Dumas 310 W. Bellevue Ave. San Mateo, CA 94402 415-412-9300 AIM: radumas [email protected] http://www.servqual.com On Dec 14, 2010, at 11:58 AM, Robert Shubert wrote: > Added to the list. > > I agree that there should be separate error files for certain groups of > errors: > > No TAF/TML file found (aka 404) > Witango Execution Can't continue (error in TAF/TML/TCF) > Configuration/Server issue (aka 5xx) > > I also don't like that the hitting the queryTimeout can't be processed as an > error and I think that the client error system needs to be updated as well. > > Robert > > -----Original Message----- > From: Roland Dumas [mailto:[email protected]] > Sent: Tuesday, December 14, 2010 12:53 PM > To: [email protected] > Subject: Re: Witango-Talk: customizing the 404 error response > > Here's a long standing problem: the 404 error page for witango. If a client > hits a nonexistent .tml or .taf URL, they get a witango-generated error. > inelegant. One should be able to customize that to the 404 error page of your > choice. Bill Conlon suggested the logic, which makes perfect sense. It will, > however, reliably crash the witango server if you actually put any code into > the error.tml file. > > (note that the thread started in 2007) > > It's annoying that a client's request for a non-gibberish 404 file can't be > met. > > > _________________________ > > Roland A. Dumas > 310 W. Bellevue Ave. > San Mateo, CA 94402 > 415-412-9300 > AIM: radumas > [email protected] > http://www.servqual.com > > > > > On Nov 14, 2008, at 3:07 PM, Roland Dumas wrote: > >> Holy Cow! When you do this, it DOES crash the witango server! >> >> On Nov 9, 2008, at 8:21 AM, Roland Dumas wrote: >> >>> Bill, >>> I never implemented this. Did it ever work for you? I'm about to give it a >>> try, but if it crashes witangod, I'll give it a second thought. >>> >>> In the config, there is no defaulterrorfile designated. I was going to crib >>> your page as you wrote it and then whip up my 404.tml file >>> >>> RAD >>> On Sep 28, 2007, at 11:57 AM, William M Conlon wrote: >>> >>>> Hi Roland, >>>> >>>> Did you get this working? I'm now trying to do something similar, and >>>> finding it's not straightforward. >>>> >>>> I have my apache configure to return notfound.tml for 404 errors, which >>>> works. But if I have missing witango file, the error handler crashes my >>>> 5.0.1.065 witango server. >>>> >>>> DEFAULTERRORFILE=/usr/local/witango/MiscFiles/error.tml >>>> >>>> My error handler, error.tml, is meant to allow a custom notfound error for >>>> each domain: >>>> >>>> <@IF EXPR="<@ERROR PART='number1'> = -3" > >>>> <@INCLUDE file="<@WEBROOT>notfound.tml"> >>>> <@ELSE> >>>> >>>> <@ERRORS> >>>> <B>Class: </B><@ERROR PART="class"><BR> >>>> <B>Application File: </B><@ERROR PART="appfilepath"><@ERROR >>>> PART="appfilename"><BR> >>>> <B>Action: </B><@ERROR PART="postion"><BR> >>>> <B>Main Error Number: </B><@ERROR PART="number1"><BR> >>>> <B>Secondary Error Number: </B><@ERROR PART="number2"><BR> >>>> <B>Main Error Message: </B><@ERROR PART="message1"><BR> >>>> <B>Secondary Error Message: </B><@ERROR PART="message2"><BR> >>>> <HR> >>>> </@ERRORS> >>>> </@IF> >>>> >>>> >>>> thanks >>>> >>>> Bill >>>> >>>> >>>> On Aug 20, 2007, at 5:25 PM, Roland Dumas wrote: >>>> >>>>> so get the error.html and insert this in it? >>>>> >>>>> >>>>> >>>>> <@IF EXPR='<@ERROR PART="number1"> = -3' > >>>>> <@INCLUDE file="/errors/404.tml"> >>>>> <@ELSE> >>>>> >>>>> <@ERRORS> >>>>> <B>Class: </B><@ERROR PART="class"><BR> >>>>> <B>Application File: </B><@ERROR PART="appfilepath"><@ERROR >>>>> PART="appfilename"><BR> >>>>> <B>Action: </B><@ERROR PART="postion"><BR> >>>>> <B>Main Error Number: </B><@ERROR PART="number1"><BR> >>>>> <B>Secondary Error Number: </B><@ERROR PART="number2"><BR> >>>>> <B>Main Error Message: </B><@ERROR PART="message1"><BR> >>>>> <B>Secondary Error Message: </B><@ERROR PART="message2"><BR> >>>>> <HR> >>>>> </@ERRORS> >>>>> >>>>> >>>>> </@IF> >>>>> >>>>> On Aug 20, 2007, at 4:35 PM, William M Conlon wrote: >>>>> >>>>>> Yes. that works on my witango5 >>>>>> >>>>>> Just evaluate the main error number to dispatch different pages. >>>>>> >>>>>> On Aug 20, 2007, at 4:31 PM, William M Conlon wrote: >>>>>> >>>>>>> I think you just edit the DEFAULTERRORFILE. >>>>>>> >>>>>>> Bill >>>>>>> >>>>>>> On Aug 20, 2007, at 4:23 PM, Roland Dumas wrote: >>>>>>> >>>>>>>> no, because witango doesn't pick up the apache 404 file. >>>>>>>> >>>>>>>> On Aug 20, 2007, at 4:21 PM, William M Conlon wrote: >>>>>>>> >>>>>>>>> You don't mean the apache 404: >>>>>>>>> >>>>>>>>> ErrorDocument 404 /notfound.html >>>>>>>>> >>>>>>>>> Bill >>>>>>>>> >>>>>>>>> >>>>>>>>> On Aug 20, 2007, at 4:17 PM, Roland Dumas wrote: >>>>>>>>> >>>>>>>>>> How can I customize the witango file not found response? I'd like it >>>>>>>>>> to just grab a page in the web site. >>>>>>>>>> ________________________________________________________________________ >>>>>>>>>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >>>>>>>>>> >>>>>>>>> ________________________________________________________________________ >>>>>>>>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >>>>>>>>> >>>>>>>>> >>>>>>>> ________________________________________________________________________ >>>>>>>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >>>>>>>> >>>>>>> ________________________________________________________________________ >>>>>>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >>>>>>> >>>>>> ________________________________________________________________________ >>>>>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >>>>>> >>>>>> >>>>> ________________________________________________________________________ >>>>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >>>>> >>>> ________________________________________________________________________ >>>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >>>> >>>> >>> ________________________________________________________________________ >>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >>> >> ________________________________________________________________________ >> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >> > > > > ---------------------------------------- > > To unsubscribe from this list, please send an email to [email protected] > with "unsubscribe witango-talk" in the body. > > > > ---------------------------------------- > > To unsubscribe from this list, please send an email to [email protected] > with "unsubscribe witango-talk" in the body. > ---------------------------------------- To unsubscribe from this list, please send an email to [email protected] with "unsubscribe witango-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to [email protected] with "unsubscribe witango-talk" in the body.
