Skip to content

[stable31] fix(proxy): validate request path before forwarding to ExApp #3451

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

[stable31] fix(proxy): validate request path before forwarding to ExApp #3451

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

tests-deploy.yml

on: pull_request
NC In Host
2m 24s
NC In Host
NC In Julius Docker
2m 39s
NC In Julius Docker
NC In Julius Docker(DSP-HTTP)
1m 43s
NC In Julius Docker(DSP-HTTP)
NC In Julius Docker(DSP-HTTPS)
2m 18s
NC In Julius Docker(DSP-HTTPS)
NC In Host(Redis)
2m 43s
NC In Host(Redis)
NC In Host(Redis) • Deploy options
2m 16s
NC In Host(Redis) • Deploy options
NC In Host(network=host)
3m 44s
NC In Host(network=host)
NC In Julius Docker(DSP-HTTPS-BRIDGE)
2m 34s
NC In Julius Docker(DSP-HTTPS-BRIDGE)
Tests-Deploy-OK
4s
Tests-Deploy-OK
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
NC In Julius Docker(DSP-HTTPS)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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: actions/checkout@c85c95e3d7251135ab7dc9ce3241c5835cc595a9, actions/upload-artifact@v4, andstor/file-existence-action@20b4d2e596410855db8f9ca21e96fbe18e12930b, shivammathur/setup-php@4bd44f22a98a19e0950cbad5f31095157cc9621b. 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 Julius Docker(DSP-HTTPS-BRIDGE)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@c85c95e3d7251135ab7dc9ce3241c5835cc595a9, actions/upload-artifact@v4, andstor/file-existence-action@20b4d2e596410855db8f9ca21e96fbe18e12930b, shivammathur/setup-php@4bd44f22a98a19e0950cbad5f31095157cc9621b. 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: actions/checkout@c85c95e3d7251135ab7dc9ce3241c5835cc595a9, actions/upload-artifact@v4, andstor/file-existence-action@20b4d2e596410855db8f9ca21e96fbe18e12930b, shivammathur/setup-php@4bd44f22a98a19e0950cbad5f31095157cc9621b. 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 Julius Docker(DSP-HTTP)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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 Julius Docker
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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: actions/checkout@c85c95e3d7251135ab7dc9ce3241c5835cc595a9, actions/upload-artifact@v4, andstor/file-existence-action@20b4d2e596410855db8f9ca21e96fbe18e12930b, shivammathur/setup-php@4bd44f22a98a19e0950cbad5f31095157cc9621b. 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.26 KB
sha256:7258ca89280e7484fd59f341ec9c2a37b46a5f64c98bd8be4d4946812c0c0411
dsp_http_container.log
940 Bytes
sha256:16ee6c6c75a6f6e33d985988c7b13d908c13ebbdff62493357d90666d08fdab0
dsp_http_nextcloud.log
7.2 KB
sha256:b3d685afa33ef54765cd3d120501f7dffffe2c69eea564336b79713bd76920f4
dsp_https_bridge_container.json
3.34 KB
sha256:f21db47623a2c7d3fa8657e215c856cf6590c701be4f2852e39d31343dbc0614
dsp_https_bridge_container.log
933 Bytes
sha256:2fefe5358174e26db02e8db3bcc13f55adfe59696b414b101a5306a6843548d8
dsp_https_bridge_haproxy.log
3.67 KB
sha256:d1f52736c8dc210c471cd58d355e98e8e9bab863307f979dcd4a96e2f27261bd
dsp_https_bridge_nextcloud.log
3.71 KB
sha256:0abd64995045aa968dbcdf892450d61696ff3cb4553072482f88b624f381a664
dsp_https_container.json
3.26 KB
sha256:af5ed1aa037ffda05e2643b5bc06a555b81b7f249a753ebe025fe64b3b67898f
dsp_https_container.log
937 Bytes
sha256:ef08337919f04a0b4a6de50e17698696bf3ff702e068d35c775635e3df5ae534
dsp_https_haproxy.log
3.69 KB
sha256:d48b36a4d318b52935b75f4c0ff81f8f472f03ee1e3ca8b5d33ee022a5ffd67c
dsp_https_nextcloud.log
5.46 KB
sha256:d6e621311cbbfc563a745e3b6ad730656f42b514dbc2f00b589f3936ceed21ae
nc_docker_app_docker_container.json
147 Bytes
sha256:9b71264d2c74dd5e5d3bc1a32e4614dacc633b4e33870cfe39605714c7e376f2
nc_docker_app_docker_container.log
936 Bytes
sha256:7e5033967e08a0c62c186f661523f0313696ac44e4c8a735cd75b09223fd5ff8
nc_docker_app_docker_nextcloud.log
6.32 KB
sha256:c0444509dbc030b65f9501d8b2dc1c3ae07b3800bc64b982a6ff10ef2bb8b6ff
nc_host_app_docker_container.json
3.22 KB
sha256:3a9a4a2f600bb57f6bf6d1dd0658b42d4011de4a9c28913d2a64252585325b7c
nc_host_app_docker_container.log
936 Bytes
sha256:ee888dad153035baec65dedab5e1ee5b1ad26e1515adf9f1bfef27a95b52bb2c
nc_host_app_docker_nextcloud.log
15 KB
sha256:27d3aeeb49d163a7930e1a818dbf54fbc31d9649be9e3dbcfc7dbab1ae4b7d5b
nc_host_app_docker_redis_container.json
3.22 KB
sha256:546fbffe992afdd84a4fdd19f443bb011780a1b0e029ce3ed86eae06e738e022
nc_host_app_docker_redis_container.log
927 Bytes
sha256:8dade96f78ff3abf219b8226ce21a9d4d78ceebb2ce79ca87f1e4a4150becb4f
nc_host_app_docker_redis_deploy_options_container.json
3.3 KB
sha256:f97bfba648708ce168a630570c1bd95981383b0c05f4724b7686fe33f8e60586
nc_host_app_docker_redis_deploy_options_container.log
940 Bytes
sha256:7ebc9b59b877c8d75adf215d35c1d30c58ea6979b025d17d5569c41eb07b9a10
nc_host_app_docker_redis_deploy_options_nextcloud.log
15.1 KB
sha256:3d73bb4fbd965d2999fed102a4cc41480a2e529f6cad77e3e5cf9eec2af583b8
nc_host_app_docker_redis_nextcloud.log
15 KB
sha256:31aba7b3a5eefe2825fcf331068eaacad1fa3a8ef677d784de877c78b010fbc2
nc_host_network_host_container.json
3.22 KB
sha256:5383f14dd64cf91800015be0d81c159512449c61367a3d6f3c407e98d60f646d
nc_host_network_host_container.log
939 Bytes
sha256:f4604be9c23863b88b7f421ceac5808a91e8625bc87f0ad93d62b8136331cff5
nc_host_network_host_nextcloud.log
15 KB
sha256:fdada48760d003394bede100184f28a4ed8e8c03bf96e875301b21febeacd49b