[JIRA] (SSPCPP-973) shibd re-downloading metadata on every restart

[peter (Jira)]

peter ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=60ad33f05dc18500704c2ef8 ) *commented* on SSPCPP-973 ( https://shibboleth.atlassian.net/browse/SSPCPP-973?atlOrigin=eyJpIjoiZTcxZGI3YTU3Yzc4NDY5YTgyZTVhYTQ4YjE5M2ZjMDEiLCJwIjoiaiJ9 )

Re: shibd re-downloading metadata on every restart ( https://shibboleth.atlassian.net/browse/SSPCPP-973?atlOrigin=eyJpIjoiZTcxZGI3YTU3Yzc4NDY5YTgyZTVhYTQ4YjE5M2ZjMDEiLCJwIjoiaiJ9 )

Not so simple, IMO: The ETag response header is there in both cases (and with identical values):

$ curl --http1.1 -sSI https://eduid.at/md/aconet-interfed.xml 2>&1 | egrep -i '^(etag|http)'
HTTP/1.1 200 OK
ETag: "4b1e931-5f7a01d2efd00"

$ curl -sSI https://eduid.at/md/aconet-interfed.xml 2>&1 | egrep -i '^(etag|http)'
HTTP/2 200 
etag: "4b1e931-5f7a01d2efd00"

I’m able to reliably repdoduce the behaviour simply by moving aside the.tag file (generated only after signature verification via HTTP/1.1) and trying again with HTTP/2 enabled on the server – no tag file is then written and future restarts will all perform signature verification.

As to the stack not supporting HTTP/2: I do see the requests using HTTP/2 when enabled on the server:

$ipv4-address - - [24/Mar/2023:18:28:46 +0000] "GET /md/aconet-interfed.xml HTTP/2.0" 304 188 "-" "shibboleth/3.4.1 OpenSAML/3.2.1 XMLTooling/3.2.3 XML-Security-C/2.0.4 Xerces-C/3.2.4 log4shib/2.0.1 libcurl/7.76.1 OpenSSL 3.0.1 14 Dec 2021"
$ipv4-address - - [24/Mar/2023:18:29:49 +0000] "GET /md/aconet-interfed.xml HTTP/2.0" 200 78768683 "-" "shibboleth/3.4.1 OpenSAML/3.2.1 XMLTooling/3.2.3 XML-Security-C/2.0.4 Xerces-C/3.2.4 log4shib/2.0.1 libcurl/7.76.1 OpenSSL 3.0.1 14 Dec 2021"

( https://shibboleth.atlassian.net/browse/SSPCPP-973#add-comment?atlOrigin=eyJpIjoiZTcxZGI3YTU3Yzc4NDY5YTgyZTVhYTQ4YjE5M2ZjMDEiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/SSPCPP-973#add-comment?atlOrigin=eyJpIjoiZTcxZGI3YTU3Yzc4NDY5YTgyZTVhYTQ4YjE5M2ZjMDEiLCJwIjoiaiJ9 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100219- sha1:ac3e918 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20230324/b007c3b9/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-c1b15e63-6bf2-4f4f-90bc-82945d612b8f
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230324/b007c3b9/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-279bd16a-25bc-44b7-874f-f684ae03749f
Type: image/png
Size: 345 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230324/b007c3b9/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-80b820d2-2955-44bd-8d87-1fe11d4bb289
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230324/b007c3b9/attachment-0005.png>