[JIRA] (IDP-1890) Property resolution not working during stale request error

Constantin Matheis (Jira) jira at shibboleth.atlassian.net
Mon Dec 20 13:52:11 UTC 2021


Constantin Matheis ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=61bcb867643e8f006a760a6a ) *commented* on IDP-1890 ( https://shibboleth.atlassian.net/browse/IDP-1890?atlOrigin=eyJpIjoiZmZhYjJiNDEwN2U0NGVkOTgxYzJhNDhmMWY2M2E2YjAiLCJwIjoiaiJ9 )

Re: Property resolution not working during stale request error ( https://shibboleth.atlassian.net/browse/IDP-1890?atlOrigin=eyJpIjoiZmZhYjJiNDEwN2U0NGVkOTgxYzJhNDhmMWY2M2E2YjAiLCJwIjoiaiJ9 )

If It’s not fixable, it would be helpful to have some sort of heads-up in error.vm, since environment is mentioned there (I haven’t testet whether the other variables are working):

##
## Velocity Template for error end-state
##
## Velocity context will contain the following properties
## flowRequestContext - the Spring Web Flow RequestContext
## profileRequestContext - root of context tree
## encoder - HTMLEncoder class
## request - HttpServletRequest
## response - HttpServletResponse
## environment - Spring Environment object for property resolution
## custom - arbitrary object injected by deployer

The stale request state can occur very often (e.g. using the back button of the browser), so developers have to think about whether using the environment variable is a good idea.

( https://shibboleth.atlassian.net/browse/IDP-1890#add-comment?atlOrigin=eyJpIjoiZmZhYjJiNDEwN2U0NGVkOTgxYzJhNDhmMWY2M2E2YjAiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/IDP-1890#add-comment?atlOrigin=eyJpIjoiZmZhYjJiNDEwN2U0NGVkOTgxYzJhNDhmMWY2M2E2YjAiLCJwIjoiaiJ9 )

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#100187- sha1:ac4c716 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20211220/b78eccc6/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-1c492005-4530-4a38-b30c-0e25cf9f474a
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211220/b78eccc6/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-4b107f17-1295-4317-be38-cd5beabf0b81
Type: image/png
Size: 425 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211220/b78eccc6/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-3ac7b11f-f912-4d85-972a-695683312b5d
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211220/b78eccc6/attachment-0005.png>


More information about the commits mailing list