1. 26 Aug, 2021 1 commit
  2. 08 Sep, 2021 1 commit
  3. 24 Aug, 2021 1 commit
  4. 03 Aug, 2021 1 commit
  5. 17 Jul, 2021 2 commits
  6. 16 Jul, 2021 1 commit
  7. 29 Apr, 2021 1 commit
  8. 21 Apr, 2021 1 commit
  9. 12 Mar, 2021 1 commit
  10. 19 Feb, 2021 1 commit
  11. 16 Feb, 2021 1 commit
  12. 11 Jan, 2021 1 commit
  13. 24 Nov, 2020 1 commit
  14. 10 Nov, 2020 1 commit
  15. 07 Oct, 2020 2 commits
  16. 24 Sep, 2020 3 commits
  17. 23 Sep, 2020 3 commits
  18. 21 Sep, 2020 1 commit
  19. 17 Sep, 2020 1 commit
  20. 07 Aug, 2020 10 commits
  21. 15 Nov, 2019 1 commit
  22. 27 Sep, 2019 2 commits
  23. 25 Jun, 2019 1 commit
    • Laurent Wouters's avatar
      Support alternative to Date header · f90a9c36135c
      Laurent Wouters authored
      The current protocol for signed request requires the use of the Date HTTP
      header. Although this works fine for clients that have full control over the
      HTTP headers they send, this is not working in the context of web browser where
      the Date HTTP headers are forbidden to be programmatically set (and therefore
      used in any meaningful way)
      https://developer.mozilla.org/en-US/docs/Glossary/Forbidden_header_name
      
      In general, this change enables the specification of a prioritized list of
      alternative for headers. In particular for the Date header, this change
      specifies a the list ['X-Cubicweb-Date', 'Date'] as an alternative to the Date
      header; meaning that when looking for the Date header, one should first look
      at the X-Cubicweb-Date header, and then if not present at the Date header. Doing
      so, it should be possible to emit signed requests from the context of a browser
      by specifying a X-Cubicweb-Date header, overriding the Date header that the
      browser may or may not set by itself.
      f90a9c36135c
  24. 06 Mar, 2019 1 commit