You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by avallen <gi...@git.apache.org> on 2015/05/03 16:28:05 UTC
[GitHub] cxf-fediz pull request: Do allow empty servlet context name for fe...
GitHub user avallen opened a pull request:
https://github.com/apache/cxf-fediz/pull/6
Do allow empty servlet context name for fediz context
Else fediz-spring at least fails when the protected application is hosted in the root context.
This is due to servletContext.getContextPath() returning the empty string for the root context, not a forward slash as one might expect.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/avallen/cxf-fediz master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cxf-fediz/pull/6.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #6
----
commit 447324c5fa937f6faac15b69ac270690b950841a
Author: Andreas Vallen <an...@gmail.com>
Date: 2015-05-03T14:21:57Z
Do allow empty servlet context name for fediz context - else fediz-spring fails when the protected application is hosted in the root context.
This is due to servletContext.getContextPath() returning the empty string in this case, not a forward slash.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cxf-fediz pull request: Do allow empty servlet context name for fe...
Posted by avallen <gi...@git.apache.org>.
Github user avallen closed the pull request at:
https://github.com/apache/cxf-fediz/pull/6
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---