New blog post: "Controller improvements"

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

New blog post: "Controller improvements"

Erik Bruchez
Administrator
All,

Here it is:

http://blog.orbeon.com/2012/09/controller-improvements.html

Enjoy,

-Erik


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: New blog post: "Controller improvements"

idwright
Hi,

This leads into a low priority question I've had on my mind for a while now.
Do you have any suggestions about how to handle the case where a service
gives a 403 permission denied?

The scenario is that you make the call to service (using
xforms:submission) which returns 403 - this is then redirected to the
error page (which is HTML and returns a status code of 200). This then
fails to parse and you can put up a generic failure message but it would
be nice to go the forbidden (or another specified) page.

If you remove the error-page directive from web.xml then you don't get
the nice page for forbidden pages (or the service for that matter) but
you do at least get the 403 error code.

Regards,
Ian

On 20/09/12 01:50, Erik Bruchez wrote:
> All,
>
> Here it is:
>
> http://blog.orbeon.com/2012/09/controller-improvements.html
>
> Enjoy,
>
> -Erik



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Re: New blog post: "Controller improvements"

Erik Bruchez
Administrator
Ian,

Thanks. This is with a milestone build, right?

The error codes should not be 200 for the not-found, error, and
unauthorized pages. I entered an issue to check this:

https://github.com/orbeon/orbeon-forms/issues/441

In addition, this seems to say that the handlers (not-found, error,
and unauthorized) should not be shown for <service> entries:

https://github.com/orbeon/orbeon-forms/issues/440

-Erik

On Thu, Sep 20, 2012 at 4:14 AM, Ian Wright <[hidden email]> wrote:

> Hi,
>
> This leads into a low priority question I've had on my mind for a while now.
> Do you have any suggestions about how to handle the case where a service
> gives a 403 permission denied?
>
> The scenario is that you make the call to service (using xforms:submission)
> which returns 403 - this is then redirected to the error page (which is HTML
> and returns a status code of 200). This then fails to parse and you can put
> up a generic failure message but it would be nice to go the forbidden (or
> another specified) page.
>
> If you remove the error-page directive from web.xml then you don't get the
> nice page for forbidden pages (or the service for that matter) but you do at
> least get the 403 error code.
>
> Regards,
> Ian
>
>
> On 20/09/12 01:50, Erik Bruchez wrote:
>>
>> All,
>>
>> Here it is:
>>
>> http://blog.orbeon.com/2012/09/controller-improvements.html
>>
>> Enjoy,
>>
>> -Erik
>
>
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing
> list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws