1. 22 Sep, 2016 1 commit
    • Upgrade xstream to 1.4.9 · e63bbed5
      Dave Syer authored
      Fixes XXE vulnerability in Eureka Server (external entity processing
      on by default in older versions of the library).
  2. 19 Sep, 2016 3 commits
  3. 15 Sep, 2016 3 commits
  4. 14 Sep, 2016 1 commit
  5. 13 Sep, 2016 2 commits
  6. 08 Sep, 2016 3 commits
  7. 07 Sep, 2016 3 commits
  8. 01 Sep, 2016 2 commits
  9. 29 Aug, 2016 2 commits
  10. 26 Aug, 2016 1 commit
  11. 22 Aug, 2016 4 commits
  12. 19 Aug, 2016 1 commit
  13. 18 Aug, 2016 1 commit
  14. 17 Aug, 2016 4 commits
  15. 16 Aug, 2016 1 commit
    • Deploying documentation to proper folder · 4552b33a
      Marcin Grzejszczak authored
      What we're missing ATM is different documentation versions for different application versions. What this change does is that it's:
      
      - finding out what is the current branch (e.g. 1.0.x)
      - finding out out what is the name of the main adoc file (e.g. spring-cloud-sleuth)
      - pulling the changes from gh-pages after checkout
      - finding out what is the list of comma separated whitelisted branches (via the `docs.whitelisted.branches` prop)
      - in gh-pages creating a folder with name of the branch  (e.g. /1.0.x)
      copying all the docs/target/generated-docs/ to that folder
      - if the branch from which we're calling the script is NOT master then we're changing the ${main.adoc}.html to index.html so that it's easier to access the docs (e.g. http://cloud.spring.io/spring-cloud-sleuth/1.0.x/)
  16. 10 Aug, 2016 2 commits
  17. 09 Aug, 2016 4 commits
  18. 03 Aug, 2016 1 commit
    • Fix an issue where the FormBodyWrapperFilter would encode the form parameters… · 8c4a49be
      Jacques-Etienne Beaudet authored
      Fix an issue where the FormBodyWrapperFilter would encode the form parameters differently than on the original request.
      
      The FormBodyWrapperFilter handles the application/x-www-form-urlencoded. In the case of requests received by curl or javascript, the FormHttpMessageConverter will reencode the parameters differently (for example, '(' will be encoded while it's not with the javascript encodeURIComponent method).
      
      While this doesn't create any problem, the content length was not properly set in HttpClientRibbonCommand. This causes the form params being stripped or the backend server would wait a long time for additional bytes depending on if the content length header was bigger/smaller than the actual data.
  19. 22 Jul, 2016 1 commit