1. 02 Nov, 2017 5 commits
  2. 01 Nov, 2017 6 commits
  3. 30 Oct, 2017 1 commit
  4. 28 Oct, 2017 2 commits
  5. 25 Oct, 2017 1 commit
  6. 24 Oct, 2017 2 commits
  7. 23 Oct, 2017 1 commit
    • Stefan Eissing's avatar
      On the trunk: · 13f6b244
      Stefan Eissing authored
        *) mod_md: v1.0.1, ServerName/Alias names from pure-http: virtual hosts are no longer
           auto-added to a Managed Domain. Error counts of jobs are presisted. When the server
           restarts (gracefully) any errored staging areas are purged to reset the signup/renewal
           process.
      
      
      
      git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1812999 13f79535-47bb-0310-9956-ffa450edef68
      13f6b244
  8. 21 Oct, 2017 2 commits
  9. 20 Oct, 2017 1 commit
  10. 18 Oct, 2017 3 commits
  11. 17 Oct, 2017 1 commit
  12. 16 Oct, 2017 5 commits
  13. 14 Oct, 2017 2 commits
    • Yann Ylavic's avatar
      Follow up to r1812193: really change MMN major. · 45fec95a
      Yann Ylavic authored
      git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1812197 13f79535-47bb-0310-9956-ffa450edef68
      45fec95a
    • Yann Ylavic's avatar
      Follow up to r1740928: including NOT_IN_PROXY in NOT_IN_DIR_LOC_FILE is both · 45529216
      Yann Ylavic authored
      incomplete and not backportable, fix it by introducing NOT_IN_DIR_CONTEXT.
      
      Per ap_check_cmd_context(), NOT_IN_DIR_LOC_FILE actually/really means "not in
      any directory context", while the definition itself does not include all the
      existing directory contexts (e.g. <Limit>, or <Proxy> before r1740928).
      
      This is a bit of a misnomer, at least, so instead of (ab)using it by adding the
      missing contexts (in an incompatible way), let's define NOT_IN_DIR_CONTEXT to
      really exclude all directory context (i.e. NOT_IN_DIR_LOC_FILE + NOT_IN_LIMIT +
      NOT_IN_PROXY) and use it wherever NOT_IN_DIR_LOC_FILE was used.
      
      This is by itself a major MMN bump (modules not compiled with this commit and
      having directives checked against NOT_IN_DIR_LOC_FILE won't be caught the same
      way by NOT_IN_DIR_CONTEXT in the new ap_check_cmd_context() code), but with the
      below change, 2.4.x should work as before:
      
      -   if ((forbidden & NOT_IN_DIR_CONTEXT) == NOT_IN_DIR_CONTEXT) {
      +   if ((forbidden & NOT_IN_DIR_LOC_FILE) == NOT_IN_DIR_LOC_FILE) {
              if (cmd->path != NULL) {
                  return apr_pstrcat(cmd->pool, cmd->cmd->name, gt,
      -                           " cannot occur within directory context", NULL);
      +                           " cannot occur within <Directory/Location/Files/Proxy> "
      +                           "section", NULL);
              }
              ...
          }
      
      
      
      git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1812193 13f79535-47bb-0310-9956-ffa450edef68
      45529216
  14. 13 Oct, 2017 1 commit
  15. 12 Oct, 2017 2 commits
  16. 11 Oct, 2017 3 commits
  17. 10 Oct, 2017 2 commits
    • Luca Toscano's avatar
      core, mod_rewrite: introduce the 'redirect-keeps-vary' note · a10865db
      Luca Toscano authored
                         to allow proper Vary header insertion when
                         dealing with a RewriteRule in a directory
                         context.
      
      This change is an attempt to fix a long standing problem,
      brought up while working on PR 58231. Our documentation clearly
      states the following:
      
      "If a HTTP header is used in a condition this header is added
      to the Vary header of the response in case the condition
      evaluates to true for the request."
      
      This is currently not true for RewriteCond/Rules working in
      a directory context, since when an internal redirect happens
      all the outstanding response headers get dropped.
      
      There might be a better solution so I am looking forward to
      hear more opinions and comments. My goal for a delicate change
      like this one would be to affect the least amount of configurations
      possible, without triggering unwanted side effects.
      
      If the solution is good for everybody tests will be written
      in the suite asap.
      
      
      
      git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1811744 13f79535-47bb-0310-9956-ffa450edef68
      a10865db
    • Lucien Gentis's avatar
      Rebuild. · 75bfe011
      Lucien Gentis authored
      
      git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1811666 13f79535-47bb-0310-9956-ffa450edef68
      75bfe011