Skip to content
CI

[1.3.x] MODCLUSTER-801 mod_proxy_cluster returns 404 now instead of 503 when there's no matching context #619

Sign in to view logs

[1.3.x] MODCLUSTER-801 mod_proxy_cluster returns 404 now instead of 503 when there's no matching context

[1.3.x] MODCLUSTER-801 mod_proxy_cluster returns 404 now instead of 503 when there's no matching context #619

Triggered via pull request December 11, 2023 10:48
@jfclerejfclere
synchronize #746
jfclere:1.3.x
Status Success
Total duration 1m 54s
Artifacts –

ci.yml

on: pull_request
Matrix: ci
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
ci (ubuntu-latest, 1.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
ci (macos-latest, 1.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
ci (windows-latest, 1.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/