Skip to content

Conversation

haslersn
Copy link

This reverts commit 60e5a5e. That commit was only required due to "executionContext" which has since been removed. See: #16310

Checklist

@kesselb kesselb added 3. to review Waiting for reviews technical debt labels Sep 14, 2023
@kesselb kesselb added this to the Nextcloud 28 milestone Sep 14, 2023
@kesselb
Copy link
Collaborator

kesselb commented Sep 14, 2023

Good finding 👍


return new RedirectResponse($this->urlGenerator->linkToRouteAbsolute(
'core.login.showLoginForm',
['clear' => true] // this param the code in login.js may be removed when the "Clear-Site-Data" is working in the browsers
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we sure it does by now?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The logout redirect still has this code, so your question is unrelated to this PR which only removes the subsequent (i.e., 2nd) redirect. See:

['clear' => true] // this param the code in login.js may be removed when the "Clear-Site-Data" is working in the browsers

@skjnldsv skjnldsv mentioned this pull request Nov 1, 2023
@haslersn
Copy link
Author

haslersn commented Nov 2, 2023

What's keeping this from getting merged?

@nickvergessen nickvergessen requested review from kesselb and removed request for rullzer November 2, 2023 09:59
@kesselb
Copy link
Collaborator

kesselb commented Nov 2, 2023

What's keeping this from getting merged?

The failing DCO check, for example.
Please rebase your branch (to pull in the latest changes from master) and sign off the commits (to pass the DCO check).

@haslersn
Copy link
Author

haslersn commented Nov 2, 2023

@kesselb is was signed off, but apparently there was a mismatch between committer email and sign-off email. Should be fixed now.

This was referenced Nov 6, 2023
This was referenced Nov 14, 2023
@blizzz blizzz modified the milestones: Nextcloud 28, Nextcloud 29 Nov 23, 2023
@Altahrim Altahrim mentioned this pull request Mar 12, 2024
@haslersn
Copy link
Author

What's now keeping this from getting merged?

@come-nc
Copy link
Contributor

come-nc commented Mar 12, 2024

I rebased for CI, I do not understand enough about this for approving, I’ll follow @kesselb lead on this one.

@kesselb
Copy link
Collaborator

kesselb commented Mar 13, 2024

Hello Hello, it's been a while and I don't remember all the details. I think the middleware was added to address the redirect cause by clear-site-data executionContext and can, as we removed executionContext again, go.

@haslersn
Copy link
Author

haslersn commented Apr 4, 2024

I think this can be merged.

@kesselb kesselb modified the milestones: Nextcloud 29, Nextcloud 30 Apr 4, 2024
This reverts commit 60e5a5e.
That commit was only required due to "executionContext" which has
since been removed. See: nextcloud#16310

Signed-off-by: Sebastian Hasler <sebastian.hasler@stuvus.uni-stuttgart.de>
@kesselb kesselb requested review from a team, ArtificialOwl and sorbaugh and removed request for a team April 4, 2024 13:53
@skjnldsv skjnldsv added 2. developing Work in progress stale Ticket or PR with no recent activity and removed 3. to review Waiting for reviews labels Jul 27, 2024
This was referenced Jul 30, 2024
This was referenced Aug 5, 2024
@skjnldsv skjnldsv mentioned this pull request Aug 13, 2024
@skjnldsv skjnldsv removed this from the Nextcloud 30 milestone Aug 14, 2024
@skjnldsv skjnldsv added this to the Nextcloud 32 milestone Jan 30, 2025
This was referenced Aug 22, 2025
This was referenced Sep 2, 2025
This was referenced Sep 25, 2025
@skjnldsv skjnldsv modified the milestones: Nextcloud 32, Nextcloud 33 Sep 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2. developing Work in progress stale Ticket or PR with no recent activity technical debt

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants