STAC browser - relative urls not supported: Protocol "" is uknown

[ttomasz]

What is the bug or the crash?

When STAC catalog has relative URLs to its children then the browser throws error Protocol "" is unknown.

I also see in debugging tools (F12) that it tries to make request to the URL exactly as it's presented i.e. without trying to resolve the relative URL based on URL from connection.

Steps to reproduce the issue

1. Add connection to STAC catalog that has relative URLs e.g.: https://pub-a8cc9feb8bdc4fdf9cbf37078dc21b8e.r2.dev/catalog.json.
2. Try to open the collection by clicking the little arrow

Versions

QGIS version	3.40.0-Bratislava
QGIS code branch	Release 3.40
Libraries
Qt version	5.15.10
Python version	3.11.9
GDAL/OGR version	3.10.0
PROJ version	9.5.0
EPSG Registry database version	v11.016 (2024-08-31)
GEOS version	3.13.0-CAPI-1.19.0
SQLite version	3.47.0
PDAL version	2.8.1
PostgreSQL client version	unknown
SpatiaLite version	5.1.0
QWT version	6.1.5
QScintilla2 version	2.14.1
OS version	KDE Flatpak runtime
Active Python plugins
QuickOSM	2.2.3
cartogram3	3.1.5
felt	3.1.5
qgis_stac	1.1.2
AnotherDXF2Shape	1.3.2
GTFS_Loader	1.0.0
zoom_level	0.3.1
qgis-maptiler-plugin	3.3.2
AnimateOsm	0.3.0
processing	2.12.99
db_manager	0.1.20
grassprovider	2.12.99
MetaSearch	0.3.6

Supported QGIS version

• I'm running a supported QGIS version according to the roadmap.

New profile

• I tried with a new QGIS profile

Additional context

Relative URLs may not be recommended but they are allowed according to the specification and work in STAC Web Browser: https://radiantearth.github.io/stac-browser/#/external/pub-a8cc9feb8bdc4fdf9cbf37078dc21b8e.r2.dev/catalog.json

[wonder-sk]

Can you try with the nightly builds please? It should be already fixed by #59199

[uclaros]

Automatic backporting to 3.40 failed though, I'll do a manual back port

[github-actions]

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

[github-actions]

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue.
Or, if you have any further questions, there are also further support channels that can help you.

[dwsilk]

@uclaros I am on QGIS 3.40.2 released late December and this is still an issue, was the manual backport to 3.40 not completed?

[uclaros]

@uclaros I am on QGIS 3.40.2 released late December and this is still an issue, was the manual backport to 3.40 not completed?

Unfortunately I neglected to do the backport on time. Here's the PR for a backport to 3.40.4 hopefully :) #60469