|
Hello Avi, The 406 status is a bit special since the spec says that the list of available variants should be returned http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.7). This behaviour has been implemented for the Directory Restlet. In this case, let the status filter replaces the provided entity by the status page is a bit annoying. If you have a look at the code of the com.noelios.restlet.StatusFilter#afterHandle method, you will see that the status page is sent only if the status is an error status and (the entity is null or the status service allows to overwrite it). By default, the status service does not allow to overwrite the provided entity. So, at this time, if you set the overwrite property of the status service, you will get the status page but the client will not receive the list of available variants. If you want both, you have to design your own status filter. I wonder if this kind of behaviour could be integrated... Any thought? Best regards, Thierry Boileau -- Restlet ~ Core developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com The 1.1 Tutorial states in section 8, Displaying Error Pages: |
- Restlet 1.1 Default Status Page on a 406 Error? Avi Flax
- Re: Restlet 1.1 Default Status Page on a 406 Error? Thierry Boileau

