sharpetronics/QGIS
1
0
Fork 0
mirror of https://github.com/qgis/QGIS.git synced 2025-10-08 00:05:09 -04:00
Code Issues Packages Projects Releases Wiki Activity

Add explanation on why we need to handle two different referer parameter strings

Browse Source
This commit is contained in:
Nyall Dawson 2024-02-14 09:57:00 +10:00
parent 52917aa30e
commit fcac6674a1
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/core/providers/sensorthings/qgssensorthingsprovider.cpp
View File

@ -286,6 +286,12 @@ QVariantMap QgsSensorThingsProviderMetadata::decodeUri( const QString &uri ) con
{
components.insert( QStringLiteral( "password" ), dsUri.password() );
}
// there's two different ways the referer can be set, so we need to check both. Which way it has been
// set depends on the widget used to create the URI. It's messy, but QgsHttpHeaders has a bunch of logic in
// it to handle upgrading old referer handling for connections created before QgsHttpHeaders was invented,
// and if we rely on that entirely then we get multiple "referer" parameters included in the URI, which is
// both ugly and unnecessary for a provider created post QgsHttpHeaders.
if ( !dsUri.param( QStringLiteral( "referer" ) ).isEmpty() )
{
components.insert( QStringLiteral( "referer" ), dsUri.param( QStringLiteral( "referer" ) ) );