Skip to content

[stable33] fix(proxy): validate request path before forwarding to ExApp #3449

[stable33] fix(proxy): validate request path before forwarding to ExApp

[stable33] fix(proxy): validate request path before forwarding to ExApp #3449

Triggered via pull request May 15, 2026 06:53
Status Success
Total duration 15m 31s
Artifacts 26

tests-deploy.yml

on: pull_request
NC In Host
1m 39s
NC In Host
NC In Julius Docker
2m 46s
NC In Julius Docker
NC In Julius Docker(DSP-HTTP)
1m 42s
NC In Julius Docker(DSP-HTTP)
NC In Julius Docker(DSP-HTTPS)
1m 52s
NC In Julius Docker(DSP-HTTPS)
NC In Host(Redis)
2m 26s
NC In Host(Redis)
NC In Host(network=host)
1m 55s
NC In Host(network=host)
NC In Julius Docker (HaRP-Bridge network)
2m 3s
NC In Julius Docker (HaRP-Bridge network)
NC In Julius Docker (HaRP-Bridge network-no FRP TLS)
1m 49s
NC In Julius Docker (HaRP-Bridge network-no FRP TLS)
NC In Host (HaRP-Host network)
1m 41s
NC In Host (HaRP-Host network)
NC In Host (Manual HaRP-Host network)
6m 37s
NC In Host (Manual HaRP-Host network)
NC In Julius Docker(DSP-HTTPS-BRIDGE)
1m 56s
NC In Julius Docker(DSP-HTTPS-BRIDGE)
NC In Host(Redis) Deploy options
1m 55s
NC In Host(Redis) Deploy options
Tests-Deploy-OK
4s
Tests-Deploy-OK
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
NC In Host
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@bf6b4fbd49ca58e4608c9c89fba0b8d90bd2a39f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
NC In Host(Redis)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@bf6b4fbd49ca58e4608c9c89fba0b8d90bd2a39f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
NC In Host (HaRP-Host network)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@bf6b4fbd49ca58e4608c9c89fba0b8d90bd2a39f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
NC In Host(network=host)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@bf6b4fbd49ca58e4608c9c89fba0b8d90bd2a39f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
NC In Host(Redis) Deploy options
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@bf6b4fbd49ca58e4608c9c89fba0b8d90bd2a39f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
NC In Host (Manual HaRP-Host network)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, shivammathur/setup-php@bf6b4fbd49ca58e4608c9c89fba0b8d90bd2a39f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
dsp_http_container.json
3.25 KB
sha256:86d57574aad7d07e9971f0887cb4a07eb6c8601b061f0d235395f07911917b07
dsp_http_container.log
938 Bytes
sha256:b977532a425ebd67bd4244d47d8c2cc875a326a32b0fa99a1910f916fb4b967d
dsp_http_nextcloud.log
590 Bytes
sha256:80a62ba0ab06079b5bf2a584fb9da5fc78b3767c46f117c7c5923a63a15d8f1d
dsp_https_bridge_container.json
3.34 KB
sha256:76c62561339bb9a518a85ba9fc512e87c67cee5b345398bdbd0e47a44362cc37
dsp_https_bridge_container.log
891 Bytes
sha256:778401551588072c67ea473818fcc6de10b6bb5bb8a6c4ce48f21cfca85b03d0
dsp_https_bridge_haproxy.log
3.69 KB
sha256:bad0f062e896e98671162ea94db79cf1dafcc15af871b13998c427372c9b60ff
dsp_https_bridge_nextcloud.log
750 Bytes
sha256:0e04a546e68f9c354ce84c55edf2cee2991be33f161292a397d50a16124ce524
dsp_https_container.json
3.28 KB
sha256:8b20ba389d7617d91c004d85dddda70f5bcefa6f17682ba28dd5e00864057924
dsp_https_container.log
884 Bytes
sha256:f80c3af0d6e49ee1546895b2162c43ac5e389e304a1a2741d8b8856256dd0f9f
dsp_https_haproxy.log
3.7 KB
sha256:b2bb72d65fe93ed7e90770aeb08907a152d7a5066c5a87b0a8c881b920014248
dsp_https_nextcloud.log
598 Bytes
sha256:7fd1864b093ea37cbbf1653155c285cf0449dac311c733b36558e523f357a182
nc_docker_app_docker_container.json
147 Bytes
sha256:ddbdc8af70e1f31c7b7d8c8d56f9f4f04c089852c3cb88bbe0ba161bc5622b8e
nc_docker_app_docker_container.log
946 Bytes
sha256:1b5e67d6b730804a7512f5835537ce5872875a2de96cc6db1c6ba87701bb0482
nc_docker_app_docker_nextcloud.log
594 Bytes
sha256:beb35c6dee0a1d7be0bed3342daf6f503afe141721266d2db095d58963706bf7
nc_host_app_docker_container.json
3.22 KB
sha256:1f9d81b86988a8f005a14ad43731557f6aa9e98cf4fef0b489e493ace0991331
nc_host_app_docker_container.log
937 Bytes
sha256:4e67bd8cb72069365826d4252e4dfb63f38e412c2dfdf6e54124827dc2578801
nc_host_app_docker_nextcloud.log
54.5 KB
sha256:3922c6f6b302dc2c232f1dadeaf79c93e4f48afd47b4487a934db9a811308792
nc_host_app_docker_redis_container.json
3.23 KB
sha256:8d0990bbe67960eae0eb0f94e5ccabced8ce82cd9c49e2056be3e93dfc6bd9a5
nc_host_app_docker_redis_container.log
938 Bytes
sha256:17777303743e6cbc2c32e5fe9bcb0c509da7922c2589528bc8b5e37bccfa7381
nc_host_app_docker_redis_deploy_options_container.json
3.3 KB
sha256:b9575678321bf19ac4cacec4cfd50d141364bf6510dc96dac1df3c6d2d450b30
nc_host_app_docker_redis_deploy_options_container.log
933 Bytes
sha256:7a42c55e1a40688fe012f121b9032adec4613aa61d5bc63d3929d0d7d98e80c4
nc_host_app_docker_redis_deploy_options_nextcloud.log
58.2 KB
sha256:0e4fe99467998a16df78ad14305a4b413a39b350e0339579222319664fb9b212
nc_host_app_docker_redis_nextcloud.log
55.1 KB
sha256:326ce9bb2ffccfa6e3a3aec3585cffd758277c2bfd9b8a70ebf2bfc3467b7748
nc_host_network_host_container.json
3.21 KB
sha256:8d5ffae18b35b7c04d490ed686d9686e95189a9f706c55240f30a91e3a99fcfc
nc_host_network_host_container.log
951 Bytes
sha256:4dda730649e8096daa999d4988d266949486173129984103c0969a0e00bf4506
nc_host_network_host_nextcloud.log
55.9 KB
sha256:d6224786316b33117e2fa150834a74b9fa2943572572f59a73ba2e52a868dac4