1. 18 Oct, 2023 11 commits
  2. 17 Oct, 2023 11 commits
    • Nils Goroll's avatar
      try to stabilize vtc · d4135153
      Nils Goroll authored
      seen in vtest:
      
      **** v1   vsl|       1004 Begin           b bereq 1003 fetch
      **** v1   vsl|       1004 VCL_use         b vcl1
      **** v1   vsl|       1004 Timestamp       b Start: 1602334643.946723 0.000000 0.000000
      **** v1   vsl|       1004 BereqMethod     b PUT
      **** v1   vsl|       1004 BereqURL        b /2
      **** v1   vsl|       1004 BereqProtocol   b HTTP/1.1
      **** v1   vsl|       1004 BereqHeader     b Host: 127.0.0.1
      **** v1   vsl|       1004 BereqHeader     b Content-Length: 250000
      **** v1   vsl|       1004 BereqHeader     b X-Forwarded-For: 127.0.0.1
      **** v1   vsl|       1004 BereqMethod     b GET
      **** v1   vsl|       1004 BereqHeader     b Accept-Encoding: gzip
      **** v1   vsl|       1004 BereqHeader     b X-Varnish: 1004
      **** v1   vsl|       1004 VCL_call        b BACKEND_FETCH
      **** v1   vsl|       1004 VCL_return      b fetch
      **** v1   vsl|       1004 BackendOpen     b 26 s1 127.0.0.1 36579 127.0.0.1 60878 connect
      **** v1   vsl|       1004 Timestamp       b Bereq: 1602334643.956883 0.010159 0.010159
      **** v1   vsl|       1004 FetchError      b HTC eof (-1)
      
      Ref #3433
      d4135153
    • Poul-Henning Kamp's avatar
    • Dridi Boukelmoune's avatar
      build: Revisit zlib C flags one more time · 0c356af2
      Dridi Boukelmoune authored
      Trying to fix the build for clang 15 actually broke the build for GCC.
      
      The -Werror that was initially set after saving CFLAGS was meant to be
      part of NO_VIZ test. We turn warnings into errors later in the configure
      script so at this point we shouldn't care about it. If we really do, we
      can move this check below the line where -Werror is set.
      
      GCC chokes on -Wno-error=deprecated-non-prototype so instead we add it
      conditionally.
      
      To match the naming convention everywhere else, libvgz_extra_cflags was
      renamed to VGZ_CFLAGS.
      
      Refs 118fd10c
      
      Conflicts:
      	configure.ac
      	lib/libvgz/Makefile.am
      0c356af2
    • Poul-Henning Kamp's avatar
    • Dridi Boukelmoune's avatar
      build: Better handle zlib-specific C flags · 2766d16a
      Dridi Boukelmoune authored
      There are two warnings that we enforce for our own code that zlib does
      not. There's also the visibility attribute that we check at configure
      time. And regarding the visibility attribute, zlib no longer relies on
      a NO_VIZ macro and aligned with the autoconf naming convention and wants
      HAVE_HIDDEN instead.
      
      Conflicts:
      	configure.ac
      	lib/libvgz/Makefile.am
      2766d16a
    • Poul-Henning Kamp's avatar
      Fix a couple of old-style functions · 149a536e
      Poul-Henning Kamp authored
      149a536e
    • Poul-Henning Kamp's avatar
      Track zlib in FreeBSD · a3431ade
      Poul-Henning Kamp authored
      a3431ade
    • Poul-Henning Kamp's avatar
      Sync libvgz with upstream zlib. · 23d6cebf
      Poul-Henning Kamp authored
      Varnish is not subject to CVE 2022 37434, we never use "extra" data.
      23d6cebf
    • Poul-Henning Kamp's avatar
      Try to fix vgz@sunos · 2b4b7070
      Poul-Henning Kamp authored
      2b4b7070
    • Poul-Henning Kamp's avatar
      Upgrade zlib to 1.2.12 · 27fe7751
      Poul-Henning Kamp authored
      27fe7751
    • Poul-Henning Kamp's avatar
      Align code with with zlib 1.2.11. · d74a55e1
      Poul-Henning Kamp authored
      FreeBSD's code is undergoing some compatibility adaptations
      so we go directly to the source from here.
      
      PS: Please keep cochinelle out of libvgz.
      d74a55e1
  3. 04 Sep, 2023 1 commit
  4. 05 Dec, 2022 1 commit
  5. 12 Oct, 2022 16 commits