Skip to content
GitLab
  1. 30 Sep, 2018 4 commits
  3. 27 Sep, 2018 5 commits
  5. 26 Sep, 2018 3 commits
  7. 23 Sep, 2018 2 commits
  9. 22 Sep, 2018 1 commit
  11. 21 Sep, 2018 2 commits
  13. 20 Sep, 2018 2 commits
  15. 18 Sep, 2018 4 commits
  17. 15 Sep, 2018 3 commits
  19. 13 Sep, 2018 1 commit
  21. 12 Sep, 2018 2 commits
  23. 11 Sep, 2018 6 commits
  25. 06 Sep, 2018 2 commits
    • Yann Ylavic's avatar
      Follow up to r1840149: core input filter pending data. · a4b9355a
      Yann Ylavic authored 
      Since r1840149 ap_core_input_filter() can't use use f->[priv->]bb directly, so
ap_filter_input_pending() stopped accounting for its pending data.

But ap_core_input_filter() can't (and doesn't need to) setaside its socket
bucket, so ap_filter_setaside_brigade() is not an option. This commit adds
ap_filter_adopt_brigade() which simply moves the given buckets (brigade) into
f->priv->bb, and since this is not something to be done blindly (the buckets
need to have c->pool/bucket_alloc lifetime, which is the case in the core
filter) the function is not AP_DECLAREd/exported thus can be used in core only.

With ap_filter_adopt_brigade() and ap_filter_reinstate_brigade(), the core
input is now ap_filter_input_pending() friendly.

Also, ap_filter_recycle() is no more part of the API (AP_DECLARE removed too),
there really is no point to call it outside core code. MAJOR bumped once again
because of this.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1840265 13f79535-47bb-0310-9956-ffa450edef68
      a4b9355a
    • Eric Covener's avatar
      fix StrictHostCheck in single/non-NVH vhosts · 929df94d
      Eric Covener authored 
      While all VH'es are NVH'es in 2.4 and later, something special happens
once a second NVH in a set is added.  This case covers the 
global server config scenario as well.



git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1840229 13f79535-47bb-0310-9956-ffa450edef68
      929df94d
  27. 05 Sep, 2018 2 commits
  29. 04 Sep, 2018 1 commit
    • Yann Ylavic's avatar
      core: follow up to r1839997: some runtime optimizations. · c5823ce8
      Yann Ylavic authored 
      We don't mind about cleaning up a connection filter when its pool is being
cleaned up already. For request filters, let pending_filter_cleanup() do
nothing if the given filter is not pending (anymore), which allows to save a
cleanup kill when the filter is removed.

Clear (zero) the reused filters (ap_filter_t) on reuse rather than cleanup,
then a single APR_RING_CONCAT() can be used to recycle dead_filters in a one
go.

Always call ap_filter_recycle() in ap_filter_output_pending(), even if no
filter is pending, and while at it fix s/ap_filter_recyle/ap_filter_recycle/
silly typo.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1840028 13f79535-47bb-0310-9956-ffa450edef68
      c5823ce8