Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WOHyperLink->WOLongResponsePage -> WORedirect caching problem #1014

Open
galmok opened this issue May 10, 2023 · 0 comments
Open

WOHyperLink->WOLongResponsePage -> WORedirect caching problem #1014

galmok opened this issue May 10, 2023 · 0 comments

Comments

@galmok
Copy link

galmok commented May 10, 2023

We have a page with a link presented as WOHyperLink that calls an action that creates a WOLongResponsePage using pageWithName and returns the page.

This works. When clicked, a new browser window is opened in which the WOLongResponsePage is running (HTML rendered, performAction called), itself calling a 3rd party site and constructs an URL that the pageForResult returns a WORedirect to.

So far so good.

The problem arises when that browser window is closed and the user again clicks on the WOHyperLink. In that case, the result from the previous WOLongResponsePage is used (i.e. redirect to previous constructed URL). No new WOLongResponsePage is created.

The third time a user clicks on the WOHyperLink, the result is the HTML is rendered as the first run, and the WOLongResponsePage isn’t created. This time however, the redirect doesn’t happen and the user is stuck at the WOLongResponsePage (that isn’t refreshing).

I feel there must be a way to signal that the original WOHyperLink result must not be cached/reused, making it always call the action that creates a new WOLongResponsePage. I just can’t see how to do this.

Any hints?

If the page with the WOHyperLink is refreshed, then a new WOLongResponsePage is created, but the user won’t know that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant