Trying to get custom page specific files from ../base1/

[chim678]

Explain what happens

I am using a small custom application inside cockpit. For the app I need these files:

<script src="../base1/cockpit.js"></script>
<script src="../base1/livesocket.js" charset="utf-8"></script>
<script src="../base1/gformat.js"></script>
<script src="../base1/dict-compare.min.js"></script>
<script src="../base1/mask-names.js"></script>
<script src="../base1/bluebird.min.js"></script>

All of those files are presented in /usr/local/share/cockpit/base1 (most of them as *.gz).
When I go to the browser and upload my app, I see that all the files are not found except cockpit.js.

For example cockpit.css:

Request URL: https://192.168.75.132/cockpit/@localhost/base1/cockpit.css
Request Method: GET
Status Code: 404 Not Found
Remote Address: 192.168.75.132:443
Referrer Policy: strict-origin-when-cross-origin

and cockpit.js:
Request URL: https://192.168.75.132/cockpit/@localhost/base1/cockpit.js
Request Method: GET
Status Code: 200 OK
Remote Address: 192.168.75.132:443
Referrer Policy: strict-origin-when-cross-origin

cockpit-ws: 300
OS: RHEL9.3
And the most interesting detail: on the RHEL9.1 everything works fine with the same cockpit version.

Tried with different versions of the cockpit and different browsers, and cleaned the cache - but nothing helped.
There are some warnings and errors in the logs, but don't see anything related to the files from /base1.

Version of Cockpit

cockpit-ws: 300

Where is the problem in Cockpit?

Applications

Server operating system

Red Hat Enterprise Linux

Server operating system version

9.3

What browsers are you using?

Chrome

System log

2023-11-20T03:32:45.909052000-05:00 cockpit.packages-WARNING: /usr/local/share/cockpit/base1/manifest.json attribute 'bridges' elements: attribute 'spawn' required
2023-11-20T03:32:45.921490000-05:00 INFO: cockpit-ws: logged in user session
2023-11-20T03:32:45.939065000-05:00 INFO: cockpit-ws: New connection to session from 172.17.1.5
2023-11-20T03:32:46.073016000-05:00 INFO: cockpit-ws: WebSocket from 172.17.1.5 for session closed
2023-11-20T03:32:47.154585000-05:00 INFO: cockpit-ws: New connection to session from 172.17.1.5
2023-11-20T03:36:20.794942000-05:00 INFO: cockpit-ws: New connection to session from 172.17.1.5
2023-11-20T03:44:51.878815000-05:00 MESSAGE: WebSocket: connection unexpectedly closed by peer
2023-11-20T03:44:51.879519000-05:00 MESSAGE: WebSocket: error closing web socket stream: Error sending data: Connection reset by peer
2023-11-20T03:44:51.879645000-05:00 INFO: cockpit-ws: WebSocket from 172.17.1.5 for session closed
2023-11-20T03:45:07.015733000-05:00 INFO: cockpit-ws: session timed out
2023-11-20T04:05:15.795680000-05:00 INFO: cockpit-ws: WebSocket from 172.17.1.5 for session closed
2023-11-20T04:05:18.752941000-05:00 INFO: cockpit-ws: New connection to session from 172.17.1.5
2023-11-20T05:45:57.807880000-05:00 INFO: cockpit-ws: WebSocket from 172.17.1.5 for session closed
2023-11-20T05:45:58.091233000-05:00 INFO: cockpit-ws: New connection to session from 172.17.1.5
2023-11-20T05:55:15.689466000-05:00 INFO: cockpit-ws: WebSocket from 172.17.1.5 for session closed
2023-11-20T05:55:16.950808000-05:00 INFO: cockpit-ws: New connection to session from 172.17.1.5
2023-11-20T06:47:32.248969000-05:00 INFO: cockpit-ws: New connection to session from 172.17.1.5
2023-11-20T07:02:50.378520000-05:00 INFO: cockpit-ws: WebSocket from 172.17.1.5 for session closed
2023-11-20T07:02:50.769923000-05:00 INFO: cockpit-ws: New connection to session from 172.17.1.5
2023-11-20T07:02:53.415547000-05:00 INFO: cockpit-ws: WebSocket from 172.17.1.5 for session closed
2023-11-20T07:02:53.979272000-05:00 INFO: cockpit-ws: New connection to session from 172.17.1.5
2023-11-20T07:13:53.144661000-05:00 INFO: cockpit-ws: WebSocket from 172.17.1.5 for session closed
2023-11-20T07:13:53.764124000-05:00 INFO: cockpit-ws: New connection to session from 172.17.1.5
2023-11-20T07:15:14.459449000-05:00 INFO: cockpit-ws: New connection to session from 172.17.1.5
2023-11-20T07:33:45.053921000-05:00 INFO: cockpit-ws: WebSocket from 172.17.1.5 for session closed
2023-11-20T07:33:46.248584000-05:00 INFO: cockpit-ws: New connection to session from 172.17.1.5

[martinpitt]

This looks rather strange to begin with -- base1/ is a directory that is shipped by cockpit-bridge. It contains cockpit.js, but none of the other files like "bluebird". These must be from your own application, so they should be in your own package directory, not ../base1. Please try to include them like src="gformat.js".

[chim678]

The problem was that, with the new cockpit-bridge, our old manifest.json stopped being served. And the /usr/local/share/cockpit/base1 was not exposed at all. we had the next configuration of the bridges:
{
"version": "@Version@",
"priority": -1,
"bridges": [
{
"match": { "superuser": "require" },
"problem": "access-denied"
},
{
"match": { "superuser": true },
"problem": "access-denied"
}
]
}
Reverting to the standard manifest.json from /usr/share/cockpit solved the problem. Not sure, to be honest, why initially the configuration was like that.

[martinpitt]

Thanks, I'm glad that you resolved the mystery!