[jira] [Comment Edited] (OLINGO-307) Issue handling the redirect in ODataServlet

["Amr Ellafy (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OLINGO-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314017#comment-14314017 ] 

Amr Ellafy edited comment on OLINGO-307 at 2/10/15 11:03 AM:
-------------------------------------------------------------

I would suggest a servlet init parameter (enableRedirect, for example)


was (Author: amrlafi@gmail.com):
I would suggest and servlet init parameter (enableRedirect, for example)

> Issue handling the redirect in ODataServlet
> -------------------------------------------
>
>                 Key: OLINGO-307
>                 URL: https://issues.apache.org/jira/browse/OLINGO-307
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata2-core
>    Affects Versions: V2 1.2.0
>            Reporter: Eugenio Lentini
>            Assignee: Christian Amend
>            Priority: Blocker
>
> Hi,
> as I have been suggested I am using the ODataServlet instead of the Cxf or Jersey one but I guess there is an issue handling the redirection.
> Basically I have a plain filter used to authorize the user before the call to the servlet. I have tested in Glassfish 3, Glassfish 4 and Jetty and the redirection works great.
> The issue appears in IBM Websphere which probably interprets the specification in a slightly different way so in ODataServlet line 91
> if (req.getPathInfo() != null) {
>       handle(req, resp, xHttpMethod, xHttpMethodOverride);
>     } else {
>       handleRedirect(req, resp);
>     }
> the req.getPathInfo() is equal to null when in Glassfish, for instance, is "/" submitting the following request
> http://localhost:9080/context-root/odata.svc/?foo=1&bar=2
> In handle redirect method there is
> ODataResponse.status(HttpStatusCodes.TEMPORARY_REDIRECT)
>           .header(HttpHeaders.LOCATION, "/").build();
> so after the redirect the request points to http://localhost:9080/ as normal, which produces in WebSphere
> Error 404: com.ibm.ws.webcontainer.servlet.exception.NoTargetForURIException: No target servlet configured for uri: /
> So I guess instead of "/" there should be something like req.getContextPath()
> Thanks a lot for the attention.
> Eugenio



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)