[JIRA] (CPPXT-156) ETag not being stored off when HTTP/2 used for metadata
peter (Jira)
jira at shibboleth.atlassian.net
Tue Apr 25 14:35:04 UTC 2023
peter ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=60ad33f05dc18500704c2ef8 ) *commented* on CPPXT-156 ( https://shibboleth.atlassian.net/browse/CPPXT-156?atlOrigin=eyJpIjoiNDlkMTcyNWY3YTBhNDUwNDkwMmZiOTk2MWNiOTUwM2EiLCJwIjoiaiJ9 )
Re: ETag not being stored off when HTTP/2 used for metadata ( https://shibboleth.atlassian.net/browse/CPPXT-156?atlOrigin=eyJpIjoiNDlkMTcyNWY3YTBhNDUwNDkwMmZiOTk2MWNiOTUwM2EiLCJwIjoiaiJ9 )
JFYI, when checking whether I could change the casing of the reponse header names for HTTP/2 usage I stumbled across the relevant RFCs. Turns out with HTTP/2 they MUST be all lowercase, so nothing to tune on the server side (except turning off HTTP/2 support, of course).
Just as in HTTP/1.x, header field names are strings of ASCII
characters that are compared in a case-insensitive fashion.
However, header field names MUST be converted to lowercase prior to their
encoding in HTTP/2.
( RFC 7540 ( https://www.rfc-editor.org/rfc/rfc7540.html#section-8.1.2 ) )
Field names MUST be converted to lowercase when constructing an HTTP/2 message.
( RFC 9113 ( https://datatracker.ietf.org/doc/html/rfc9113#section-8.2 ) )
( https://shibboleth.atlassian.net/browse/CPPXT-156#add-comment?atlOrigin=eyJpIjoiNDlkMTcyNWY3YTBhNDUwNDkwMmZiOTk2MWNiOTUwM2EiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/CPPXT-156#add-comment?atlOrigin=eyJpIjoiNDlkMTcyNWY3YTBhNDUwNDkwMmZiOTk2MWNiOTUwM2EiLCJwIjoiaiJ9 )
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#100223- sha1:cdc0af3 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20230425/3bacb1ec/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-1e0bc36d-11b3-42db-ad06-f2d176a8cff7
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230425/3bacb1ec/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-7683d8af-f4e4-4691-a406-380e0c6f21dd
Type: image/png
Size: 345 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230425/3bacb1ec/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-7002337b-f169-47b1-8a3e-5bbd53419cc1
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20230425/3bacb1ec/attachment-0005.png>
More information about the commits
mailing list