Yes, that is exactly what I am planning to do. Now the trick seems to be to send a 404 if the page does not exist. The PageSpecificationResolver throws a generic ApplicationRuntimeException if it can not find the page. How to send a 404 without modifying the Tapestry core library.
Marcel On 3/18/06, Korbinian Bachl <[EMAIL PROTECTED]> wrote: > > Hi, > > the correct way to handel this is a code 404 - if you ever go on any > static > unix/ linux webserver and misstype the case, youll get a 404. > > And if the programmer of the spider is not keen enough of this its just > his > problem. > > BTW: Even google itself for example handles it this way: > > valid: http://www.google.de/imghp?hl=de&tab=wi&q= > non valid (404): http://www.google.de/Imghp?hl=de&tab=wi&q= > > Regards, > > Korbinian > > PS: the spider-programmer soon will see that he gets loads and loads of > 404s > this way and eventually see that he may have a bug in his spider > > > -----Ursprüngliche Nachricht----- > > Von: Marcel Schepers [mailto:[EMAIL PROTECTED] > > Gesendet: Samstag, 18. März 2006 11:45 > > An: Tapestry users > > Betreff: how to deal with case sensitivity > > > > Hello, > > > > I have a Tapestry 3.0.3 application running on Windows 2003 > > Server. The application has a bookmarkable page 'ShowVacancy' > > which requires a String parameter. I have pasted such an URL > > as an example. > > > > http://www.jobstoday.nl/app?service=external/ShowVacancy&sp=Sd > 315d5a00a02bfd0010a090644fb0014 > > > > Now the site is being spidered by a fairly strange spider. It > > has all the information that is required, including a valid > > vacancy identifier, however for some reason it uses only > > URL's consisting of lower case characters, the url used by > > this spider is: > > > > http://www.jobstoday.nl/app?service=external/showvacancy&sp=sd > 315d5a00a02bfd0010a090644fb0014 > > ('showvacancy' instead of 'ShowVacancy' and 'sd....' instead > > of 'Sd...') > > > > I do not know why the spider converts valid mixed case URLs > > to lower case only URLs, but I looking for a strategy to > > handle this. At the moment the application's exception page > > is shown. But I am not satisfied with the Exception page. > > There is no exception, a 404 would be better, won't it? What > > is the correct way to handle this? > > > > Have a nice day, > > Marcel > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
