1. 06 Jun, 2008 11 commits
  2. 05 Jun, 2008 4 commits
  3. 03 Jun, 2008 2 commits
  4. 02 Jun, 2008 2 commits
  5. 01 Jun, 2008 1 commit
  6. 31 May, 2008 4 commits
  7. 30 May, 2008 2 commits
  8. 29 May, 2008 4 commits
  9. 28 May, 2008 6 commits
  10. 27 May, 2008 4 commits
    • Roy T. Fielding's avatar
      backported in r660756 · 449a6840
      Roy T. Fielding authored
      git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@660757 13f79535-47bb-0310-9956-ffa450edef68
      449a6840
    • Eric Covener's avatar
      backported to 2.2.x in r660728 · f9bc8e75
      Eric Covener authored
      
      git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@660729 13f79535-47bb-0310-9956-ffa450edef68
      f9bc8e75
    • Ruediger Pluem's avatar
      * mod_proxy_http.c · 955832af
      Ruediger Pluem authored
         Ensure that the EOC bucket is inserted BEFORE an EOS bucket in bb as
         some resource filters like mod_deflate pass everything up to the EOS
         down the chain immediately and sent the remainder of the brigade later
         (or even never). But in this case the ap_http_header_filter does not
         get out of our way soon enough.
      
         http_filters.c
         Remove all data buckets that are in a brigade after an EOC bucket
         was seen, as an EOC bucket tells us that no (further) resource
         and protocol data should go out to the client. OTOH meta buckets
         are still welcome as they might trigger needed actions down in
         the chain (e.g. in network filters like SSL).
         Remark 1: It is needed to dump ALL data buckets in the brigade
                   since an filter in between might have inserted data
                   buckets BEFORE the EOC bucket sent by the original
                   sender and we do NOT want this data to be sent.
         Remark 2: Dumping all data buckets here does not necessarily mean
                   that no further data is send to the client as:
                   1. Network filters like SSL can still be triggered via
                      meta buckets to talk with the client e.g. for a
                      clean shutdown.
                   2. There could be still data that was buffered before
                      down in the chain that gets flushed by a FLUSH or an
                      EOS bucket.
      
      PR: 37770
      
      
      git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@660726 13f79535-47bb-0310-9956-ffa450edef68
      955832af
    • Roy T. Fielding's avatar
      part of ab sync · acd03f4b
      Roy T. Fielding authored
      git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@660697 13f79535-47bb-0310-9956-ffa450edef68
      acd03f4b