about summary refs log tree commit diff
path: root/pkgs/servers/http
Commit message (Collapse)AuthorAge
* tomcat_connectors: 1.2.46 -> 1.2.48R. RyanTM2020-03-14
|
* Merge pull request #82290 from helsinki-systems/upd/ngx_fastcgi_cache_purgeMario Rodas2020-03-13
|\ | | | | nginxModules.fastcgi-cache-purge: 2.3 -> 2.5
| * nginxModules.fastcgi-cache-purge: 2.3 -> 2.5ajs1242020-03-10
| | | | | | | | switch to a fork that seems sort of alive
* | unit: 1.15.0 -> 1.16.0Izorkin2020-03-12
|/
* Merge pull request #80182 from dirkx/Redwax-0.22-updateAaron Andersen2020-02-22
|\ | | | | redwax-modules: 0.2.1 -> 0.2.2/0.2.3
| * redwax-modules: 0.2.1 -> 0.2.2/0.2.3Dirk-Willem van Gulik2020-02-21
| |
* | mod_wsgi: 4.7.0 -> 4.7.1R. RyanTM2020-02-19
|/
* Merge staging into staging-nextFrederik Rietdijk2020-02-11
|\
| * ruby_2_4: removezimbatm2020-02-10
| | | | | | | | | | | | | | | | | | | | | | | | | | According to https://endoflife.software/programming-languages/server-side-scripting/ruby ruby 2.4 will go end-of-life in march, where the new release of nixpkgs will be cut. We won't be able to support it for security updates. Remove all references to ruby_2_4 and add ruby_2_7 instead where missing. Mark packages that depend on ruby 2.4 as broken: * chefdk * sonic-pi
* | unit: 1.14.0 -> 1.15.0R. RyanTM2020-02-10
|/
* Merge master into staging-nextFrederik Rietdijk2020-02-09
|\
| * lighttpd: 1.4.54 -> 1.4.55R. RyanTM2020-02-08
| |
* | Merge #66528: glibc: 2.27 -> 2.30 (into staging)Vladimír Čunát2020-02-05
|\ \ | |/ |/| | | | | Includes update of stdenv bootstap tools (for three main platforms) and many package fixes with new glibc.
| * lwan: 0.2 -> 0.3, fix build w/glibc-2.30Maximilian Bosch2020-02-01
| |
* | openresty: rebase on top of nginx packageEmily2020-02-04
| | | | | | | | | | | | The primary motivation of this change was to allow third-party modules to be used with OpenResty, but it also results in a significant reduction of code duplication.
* | nginxModules.brotli: v0.1.2 -> unstableEmily2020-02-04
| | | | | | | | The fork was merged back upstream but has yet to see a formal release.
* | Merge pull request #78185 from dtzWill/update/nginx-1.17.8Will Dietz2020-02-03
|\ \ | |/ |/| nginxMainline: 1.17.3 -> 1.17.8
| * nginxMainline: 1.17.3 -> 1.17.8Will Dietz2020-01-21
| | | | | | | | http://nginx.org/en/CHANGES
* | Merge pull request #78265 from Synthetica9/https-homepagesSilvan Mosberger2020-01-27
|\ \ | | | | | | treewide: fix redirected urls
| * | treewide: fix redirected urlsPatrick Hilhorst2020-01-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | According to https://repology.org/repository/nix_unstable/problems, we have a lot of packages that have http links that redirect to https as their homepage. This commit updates all these packages to use the https links as their homepage. The following script was used to make these updates: ``` curl https://repology.org/api/v1/repository/nix_unstable/problems \ | jq '.[] | .problem' -r \ | rg 'Homepage link "(.+)" is a permanent redirect to "(.+)" and should be updated' --replace 's@$1@$2@' \ | sort | uniq > script.sed find -name '*.nix' | xargs -P4 -- sed -f script.sed -i ```
* | | jetty: 9.4.24.v20191120 -> 9.4.25.v20191220R. RyanTM2020-01-21
| |/ |/|
* | Merge pull request #76537 from Izorkin/unitJörg Thalheim2020-01-21
|\ \ | |/ |/| unit: 1.13.0 -> 1.14.0
| * unit: add drop capabilites patchIzorkin2019-12-26
| |
| * unit: 1.13.0 -> 1.14.0Izorkin2019-12-26
| |
* | lwan: 0.1 -> 0.2Leonhard Markert2020-01-16
| |
* | Merge pull request #77326 from aanderse/apacheHttpdAaron Andersen2020-01-15
|\ \ | | | | | | nixos/httpd: symlink apache configuration to /etc/httpd/httpd.conf for use in the apachectl command
| * | nixos/httpd: symlink apache configuration to /etc/httpd/httpd.conf for use ↵Aaron Andersen2020-01-08
| | | | | | | | | | | | in the apachectl command
* | | Merge pull request #77011 from r-ryantm/auto-update/mod_wsgiMario Rodas2020-01-09
|\ \ \ | | | | | | | | mod_wsgi: 4.6.8 -> 4.7.0
| * | | mod_wsgi: 4.6.8 -> 4.7.0R. RyanTM2020-01-05
| |/ /
* | | Merge pull request #76417 from dirkx/redwax-modulesAaron Andersen2020-01-07
|\ \ \ | |/ / |/| | mod_ca, mod_crl, mod_csr, mod_ocsp, mod_scep, mod_pkcs12, mod_spkac, mod_timestamp: init at 0.2.1
| * | Additional redwax modules - including comments from review on #75620.Dirk-Willem van Gulik2019-12-24
| | |
* | | Merge pull request #61722 from Izorkin/pinba-nginxRyan Mulligan2020-01-04
|\ \ \ | | | | | | | | nginxModules.pinba: init at 13.05.2019
| * | | nginxModules.pinba: init at 13.05.2019Izorkin2019-12-11
| | | |
* | | | Merge master into staging-nextFrederik Rietdijk2020-01-03
|\ \ \ \
| * \ \ \ Merge Last-Modified fix for nginx (#76697)aszlig2020-01-02
| |\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes the patch for nginx to clear the Last-Modified header if a static file is served from the Nix store. So far we only used the ETag from the store path, but if the Last-Modified header is always set to "Thu, 01 Jan 1970 00:00:01 GMT", Firefox and Chrome/Chromium seem to ignore the ETag and simply use the cached content instead of revalidating. Alongside the fix, this also adds a dedicated NixOS VM test, which uses WebDriver and Firefox to check whether the content is actually served from the browser's cache and to have a more real-world test case.
| | * | | | nginx: Clear Last-Modified if ETag is from storeaszlig2019-12-30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is what I've suspected a while ago[1]: > Heads-up everyone: After testing this in a few production instances, > it seems that some browsers still get cache hits for new store paths > (and changed contents) for some reason. I highly suspect that it might > be due to the last-modified header (as mentioned in [2]). > > Going to test this with last-modified disabled for a little while and > if this is the case I think we should improve that patch by disabling > last-modified if serving from a store path. Much earlier[2] when I reviewed the patch, I wrote this: > Other than that, it looks good to me. > > However, I'm not sure what we should do with Last-Modified header. > From RFC 2616, section 13.3.4: > > - If both an entity tag and a Last-Modified value have been > provided by the origin server, SHOULD use both validators in > cache-conditional requests. This allows both HTTP/1.0 and > HTTP/1.1 caches to respond appropriately. > > I'm a bit nervous about the SHOULD here, as user agents in the wild > could possibly just use Last-Modified and use the cached content > instead. Unfortunately, I didn't pursue this any further back then because @pbogdan noted[3] the following: > Hmm, could they (assuming they are conforming): > > * If an entity tag has been provided by the origin server, MUST > use that entity tag in any cache-conditional request (using If- > Match or If-None-Match). Since running with this patch in some deployments, I found that both Firefox and Chrome/Chromium do NOT re-validate against the ETag if the Last-Modified header is still the same. So I wrote a small NixOS VM test with Geckodriver to have a test case which is closer to the real world and I indeed was able to reproduce this. Whether this is actually a bug in Chrome or Firefox is an entirely different issue and even IF it is the fault of the browsers and it is fixed at some point, we'd still need to handle this for older browser versions. Apart from clearing the header, I also recreated the patch by using a plain "git diff" with a small description on top. This should make it easier for future authors to work on that patch. [1]: https://github.com/NixOS/nixpkgs/pull/48337#issuecomment-495072764 [2]: https://github.com/NixOS/nixpkgs/pull/48337#issuecomment-451644084 [3]: https://github.com/NixOS/nixpkgs/pull/48337#issuecomment-451646135 Signed-off-by: aszlig <aszlig@nix.build>
* | | | | | Merge master into staging-nextFrederik Rietdijk2020-01-02
|\| | | | |
| * | | | | unit: add withRuby_2_7 optionzimbatm2020-01-01
| |/ / / /
* | | | | treewide: configureFlags is a flat listRobin Gloster2019-12-31
| | | | |
* | | | | treewide: *inputs are listsRobin Gloster2019-12-31
| | | | |
* | | | | treewide: NIX_*_FLAGS -> stringRobin Gloster2019-12-31
| | | | |
* | | | | treewide: NIX_*_COMPILE -> stringRobin Gloster2019-12-31
| | | | |
* | | | | treewide: installFlags is a listRobin Gloster2019-12-30
|/ / / /
* | | / maintainer-list.nix: remove ndowensNathan2019-12-26
| |_|/ |/| |
* | | h2o: build with opensslJörg Thalheim2019-12-21
| |/ |/| | | | | | | otherwise we get symbol conflicts, once we link it against applications using openssl
* | Merge staging-next into stagingFrederik Rietdijk2019-12-10
|\|
| * rdf4store: remove pkg and service modulesRenaud2019-12-08
| | | | | | (#74214)
* | Merge pull request #73491 from Izorkin/unitFrederik Rietdijk2019-12-05
|\ \ | |/ |/| unit: 1.12.0 -> 1.13.0
| * unit: update build configurationIzorkin2019-11-24
| |
| * unit: 1.12.0 -> 1.13.0Izorkin2019-11-24
| |
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-24 06:16:09 +0000