[gdal-dev] Expiring token during paging on the WFS

[Andrew C Aitchison]

On Thu, 28 Mar 2024, Michael Otto via gdal-dev wrote:

> Hello,
>
> I have an important question about the use of a 'GDAL_HTTP_HEADER_FILE'.
>
> If I request a WFS with "OGR_WFS_PAGING_ALLOWED=ON" and use a header file
> for authentication, will the header file be read with every new page?
>
> I am wondering how I should deal with an expiring bearer token (validity
> 5min) with a very long lasting query (>5min).

Is this for one WFS service, or many ?
Assuming you are consuming the data promptly and aren't overloaded,
I would discuss this with the WFS service; you probably aren't
the only one having this issue. If sending the data takes longer
than the life of the token, they need longer-lived tokens.

Sorry I can't help with your actual questions.

> Questions:
> Does ogr2ogr query the header file again for each new page?
> Can I possibly set the authentication for every single requested page?
> Is there another way to deal with expiring tokens?
>
> Michael
>
> PS:
> I use Java and start the apps via the ProcessBuilder.
> If the header file is re-read for each page, I could update it accordingly
> (preferably without conflicts due to simultaneous reading and writing ;o)
> ).


-- 
Andrew C. Aitchison                      Kendal, UK
                    andrew at aitchison.me.uk