summary refs log tree commit diff
path: root/pkgs/servers/http
Commit message (Collapse)AuthorAge
* 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
| |
* | jetty: 9.4.22.v20191022 -> 9.4.24.v20191120 (#74417)R. RyanTM2019-11-30
| | | | | | | | | | | | * jetty: 9.4.22.v20191022 -> 9.4.24.v20191120 * jetty: homepage over https
* | nginx: reference testsJörg Thalheim2019-11-29
| |
* | Add nginx perl modules (#73198)tekeri2019-11-27
|/ | | | | | * nginx: enable perl_module if perl is given * nginx: move `perl = null` to toplevel
* jetty: 9.4.16.v20190411 -> 9.4.22.v20191022R. RyanTM2019-11-06
| | | (#72533)
* Merge pull request #70365 from jglukasik/mod_tileAaron Andersen2019-11-05
|\ | | | | apacheHttpdPackages.mod_tile: init at unstable-2017-01-08
| * apacheHttpdPackage.mod_tile: init at unstable-2017-01-08Joseph Lukasik2019-11-01
| |
* | mod_wsgi: 4.6.7 -> 4.6.8R. RyanTM2019-10-21
| | | | | | | | | | | | | | Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/mod_wsgi/versions
* | tengine: 2.3.1 -> 2.3.2 (#70574)Mario Rodas2019-10-15
| | | | | | | | | | | | | | | | * tengine: 2.3.1 -> 2.3.2 Changelog: https://github.com/alibaba/tengine/releases/tag/2.3.2 * tengine: unbreak
* | Merge pull request #70527 from Izorkin/nginx-unitRenaud2019-10-09
|\ \ | | | | | | unit: 1.11.0 -> 1.12.0
| * | unit: 1.11.0 -> 1.12.0Izorkin2019-10-06
| |/
* / treewide: mark some broken packages as brokenLinus Heckemann2019-10-08
|/ | | | | | | | | Refs: e6754980264fe927320d5ff2dbd24ca4fac9a160 1e9cc5b9844ef603fe160e9f671178f96200774f 793a2fe1e8bb886ca2096c5904e1193dc3268b6d c19cf65261639f749012454932a532aa7c681e4b f6544d618f30fae0bc4798c4387a8c7c9c047a7c
* Merge pull request #69715 from r-ryantm/auto-update/openrestyRyan Mulligan2019-09-28
|\ | | | | openresty: 1.15.8.1 -> 1.15.8.2
| * openresty: 1.15.8.1 -> 1.15.8.2R. RyanTM2019-09-27
| | | | | | | | | | | | | | Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/openresty/versions
* | Merge branch 'master' into staging-nextVladimír Čunát2019-09-24
|\|
| * unit: 1.10.0 -> 1.11.0Izorkin2019-09-22
| |
* | Re-Revert "Merge branch 'staging-next'"Vladimír Čunát2019-09-22
|/ | | | This reverts commit f8a8fc6c7c079de430fa528f688ddac781bcef16.
* Revert "Merge branch 'staging-next'"Vladimír Čunát2019-09-21
| | | | | | | This reverts commit 41af38f3728bd64b80721c44ed1fb019978cbc1b, reversing changes made to f0fec244ca380b9d3e617ee7b419c59758c8b0f1. Let's delay this. We have some serious regressions.
* Merge branch 'staging-next'Vladimír Čunát2019-09-21
|\
| * treewide: replace mysql.connector-c to libmysqlclientIzorkin2019-09-09
| |
* | h2o: 2.2.6 -> 2.3.0-beta2, enable multi-outputAustin Seipp2019-09-19
|/ | | | | | | | | | This also lets us remove a hack for supporting LibreSSL 2.7, since we're now using 2.9 by default, anyway. Finally, use Ninja to run the CMake build instead of Make -- speeds things up for me by a few seconds. Signed-off-by: Austin Seipp <aseipp@pobox.com>
* treewide: remove redundant quotesvolth2019-09-08
|
* Merge remote-tracking branch 'upstream/gcc-8' into staging-nextFrederik Rietdijk2019-09-08
|\ | | | | | | Earlier the gcc8 branch was merged instead of the gcc-8 branch (note the dash)...
| * Merge remote-tracking branch 'origin/master' into gcc-8Franz Pletz2019-09-03
| |\
| * \ Merge remote-tracking branch 'upstream/master' into gcc-8Robin Gloster2019-08-25
| |\ \
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-06-13 00:34:37 +0000