12 Feb, 2015
1 commit
-
git-svn-id: https://svn.forgerock.org/openig/trunk@895 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
09 Feb, 2015
7 commits
-
`HttpClient` is closing the `exchange.response` object before executing the request. When the `OAuth2ClientFilter` populates the `user_info` attribute (requesting user's profile on the AS), or communicate with the AS, it reuses the `Exchange`, change the request object, but keep the response reference. So, when the modified exchange goes through `HttpClient`, any existing response gets emptied. This fix simply nullify the `exchange.response` reference *before* sending that to the AS. That prevents `HttpClient` to cleanup the response too eagerly. git-svn-id: https://svn.forgerock.org/openig/trunk@891 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@890 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@889 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@888 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@887 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@886 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@885 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
05 Feb, 2015
2 commits
-
git-svn-id: https://svn.forgerock.org/openig/trunk@883 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@882 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
04 Feb, 2015
5 commits
-
git-svn-id: https://svn.forgerock.org/openig/trunk@880 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@879 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
The correct way to handle the \\ in the JUEL expressions is to write it like that : ${'\\\\'}. git-svn-id: https://svn.forgerock.org/openig/trunk@878 dbb9e58e-28e6-4ce0-90e8-f11d9605b710 -
git-svn-id: https://svn.forgerock.org/openig/trunk@877 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@876 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
03 Feb, 2015
7 commits
-
This tests was expecting a NPE that was thrown by `new StringReader()`. We were never going into the `readJson()` method... git-svn-id: https://svn.forgerock.org/openig/trunk@874 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@873 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
The soon-to-come Http framework needs a subset of the features provided by `Json`: only what is related to JSON parsing/writing. Everything else is related to `JsonValue` or more OpenIG specific types like `Heap`, `Expression`, ... So this is just a simple split, we now have: * `Json`: JSON parsing * `JsonValues`: OpenIG-related code git-svn-id: https://svn.forgerock.org/openig/trunk@872 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
Created a new class in utils for the StandardCharsets. When we will move to java 7, we just need to remove this file and update the package names to java.nio.charset.StandardCharsets. git-svn-id: https://svn.forgerock.org/openig/trunk@871 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@870 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@869 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@868 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
29 Jan, 2015
3 commits
-
if doable, the expression string input. As OPENIG-394 introduces the original string used in Expression, we are now able to have more explicit error messages. - 'Standardized' all expressions error messages. git-svn-id: https://svn.forgerock.org/openig/trunk@865 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@864 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@863 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
27 Jan, 2015
1 commit
-
git-svn-id: https://svn.forgerock.org/openig/trunk@859 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
23 Jan, 2015
5 commits
-
git-svn-id: https://svn.forgerock.org/openig/trunk@854 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@853 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@852 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@851 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@850 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
22 Jan, 2015
3 commits
-
git-svn-id: https://svn.forgerock.org/openig/trunk@845 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@844 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
As the URI rebasing is done at different places in the code we'd like to have a BaseUriHandler/Filter in order to factor out the code. Following the same scheme as the "Timer" decorator, the "baseURI" decorator is created by default in the Gateway Servlet. (Named "baseUri" and created at startup time in the top-level heap.) * GatewayServlet.class, Route.class The creation of the "baseUri" decorator means the attribute class 'baseURI' is no longer needed as the URI rebasing is now directly done by the decorator. In the other hand, the heap initialization performed within both class constructors, contained a list of reservedFieldNames where the 'baseURI'was present. It has been removed from there as it is now a global decorator. * RouteTest.java Removed unit test 'testRouteIsRebasingTheRequestUri'(Duplicated in the RouteBuilder test, and the RouteBuilder has the responsability to apply decorators). git-svn-id: https://svn.forgerock.org/openig/trunk@843 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
20 Jan, 2015
1 commit
-
The previous commit introduced a regression, especially for GET messages being sent with an empty entity where they should have no entity at all. They were being falsely detected as messages with content because we were comparing `EMPTY_STREAM` with `Entity.head` (the branched content) instead of the `Entity.trunk` (`head` being re-created every time OpenIG tries to read the content, so in the `HttpBasicAuthFilter` for example, we push the Entity, then delegates to the next handler in chain, so when message is sent, the `head` is != from the `trunk` and cannot be == to `EMPTY_STREAM`) I could not reliably reproduce that in a unit test with a real HTTP Server because the failure also need the HTTPClient to re-use the same connection for 2 consecutive messages. Thus, I only added a small `Entity` unit test to make sure that `Entity.mayContainData()` behave correct even when the entity is pushed/popped. git-svn-id: https://svn.forgerock.org/openig/trunk@838 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
19 Jan, 2015
3 commits
-
IDE Eclipse divided by two the spaces length when special chars are used in the line. I choose to trust the IDE instead of checkstyle and diff, my mistake. Output is fine with IntelliJ. Looks like a bug in eclipse. git-svn-id: https://svn.forgerock.org/openig/trunk@837 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
CR-5814 OPENIG-438 Document Expression plugins Respond to review comments from Guillaume. git-svn-id: https://svn.forgerock.org/openig/trunk@836 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
Added unit tests for unicode usage. git-svn-id: https://svn.forgerock.org/openig/trunk@835 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
16 Jan, 2015
2 commits
-
The toString() method is now implemented and tested. We also decide to replace Expression constructor by a more conventional valueOf(...) factory method. A new Expression is now created by Expression exp = Expression.valueOf(<Expression string>); git-svn-id: https://svn.forgerock.org/openig/trunk@834 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
The `Entity.isEmpty()` method relied on `InputStream.available()` returning something different of `0` (zero) to detect if the entity was empty or not. This technic is not reliable enough since the javadoc clearly states that this return the number of bytes that can be read **without blocking**, that means that the result of this method depends on the network (and to some extension to the web container), not entirely on the message. The idea here is to now check if the wrapped stream is the `EMPTY_STREAM` instance to detect if the entity is empty or not. This is better than the old solution because we don't rely anymore on an external `InputStream` implementation, but that will not detect a user provided stream with no data inside. This is why `isEmpty()` has been renamed to `mayContainData()`. There is also a new `setEmpty()` method to mark the entity as empty (simply assign `EMPTY_STREAM` to the wrapped stram field). git-svn-id: https://svn.forgerock.org/openig/trunk@833 dbb9e58e-28e6-4ce0-90e8-f11d9605b710