[JIRA] (SSPCPP-973) ETag not being stored off when HTTP/2 used for metadata

[peter (Jira)]

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

Re: ETag not being stored off when HTTP/2 used for metadata ( https://shibboleth.atlassian.net/browse/SSPCPP-973?atlOrigin=eyJpIjoiYzRiMmRlZGY1YzIzNDBhMmE3ZmI2M2FhMWQ3YTRkMjgiLCJwIjoiaiJ9 )

> 
> 
> 
> We haven’t ever tested anything on HTTP/2 so I imagine that’s the bug. I'm
> surprised it’s working at all.
> 
> 

🙂

Our newly rebuilt server hosting the metadata simply was following some generic template that in our case activates HTTP/2 by default these days. It’s simple to turn off (and I will, once you say you don’t need https://eduid.at/ ( https://eduid.at/ ) to easily test things; I imagine there must be other set services out there w/o you having to stand up a server with test this with).

> 
> 
> 
> That suggests a direction at least but will make debugging it harder since
> I don’t have HTTP/2 library support for the Windows build.
> 
> 

ACK. I certainly don’t insist on supporting HTTP/2 and the current state (or rather future) of that whole software stack doesn’t warrant investing much/any work here. But knowing it does not work over HTTP/2 (and leaving it at that, which is what I’m suggesting here) might warrant issuing a limited advisory of some sorts. To warn people still publishing (large) aggregates that this will cause the SP to show the behaviour reported here.

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

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/20230325/f614b710/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-64ba7ca6-3259-45b5-82bb-207230856bb9
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230325/f614b710/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-f84ab9cb-e8b9-4981-b14f-13bf28c4f0e2
Type: image/png
Size: 345 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230325/f614b710/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-41acce61-eefa-4bbc-a967-6495cbebfc9d
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230325/f614b710/attachment-0005.png>