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

fix: fix redirect URL for PUSH with websocket transport #20666

Merged
merged 4 commits into from
Dec 11, 2024

Conversation

mcollovati
Copy link
Collaborator

Description

When PUSH is enabled with web socket transport, the redirect URL to be used after a successful login is not correctly computed because it is based on the PUSH servlet mapping.
This change detects the situation and computes the correct URL.

Fixes #20575

Type of change

  • Bugfix
  • Feature

Checklist

  • I have read the contribution guide: https://vaadin.com/docs/latest/guide/contributing/overview/
  • I have added a description following the guideline.
  • The issue is created in the corresponding repository and I have referenced it.
  • I have added tests to ensure my change is effective and works as intended.
  • New and existing tests are passing locally with my change.
  • I have performed self-review and corrected misspellings.

Additional for Feature type of change

  • Enhancement / new feature was discussed in a corresponding GitHub issue and Acceptance Criteria were created.

When PUSH is enabled with websocket transport, the redirect URL to be used
after a successfull login is not correctly computed because it is based
on the PUSH servlet mapping.
This change detects the situation and computes the correct URL.

Fixes #20575
Copy link

github-actions bot commented Dec 10, 2024

Test Results

1 159 files  + 1  1 159 suites  +1   1h 33m 37s ⏱️ + 1m 14s
7 546 tests +26  7 492 ✅ +25  54 💤 +1  0 ❌ ±0 
7 871 runs   - 10  7 810 ✅  -  9  61 💤  - 1  0 ❌ ±0 

Results for commit 37a69c0. ± Comparison against base commit 7b4052d.

♻️ This comment has been updated with latest results.

Copy link
Contributor

@caalador caalador left a comment

Choose a reason for hiding this comment

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

Tested and this fixes the return url to not contain VAADIN/push after fix

@caalador caalador merged commit 33ccf17 into main Dec 11, 2024
26 checks passed
@caalador caalador deleted the issues/20575-nav-websocket-login-redirect-url branch December 11, 2024 10:58
vaadin-bot pushed a commit that referenced this pull request Dec 11, 2024
When PUSH is enabled with websocket transport, the redirect URL to be used
after a successfull login is not correctly computed because it is based
on the PUSH servlet mapping.
This change detects the situation and computes the correct URL.

Fixes #20575
vaadin-bot pushed a commit that referenced this pull request Dec 11, 2024
When PUSH is enabled with websocket transport, the redirect URL to be used
after a successfull login is not correctly computed because it is based
on the PUSH servlet mapping.
This change detects the situation and computes the correct URL.

Fixes #20575
vaadin-bot pushed a commit that referenced this pull request Dec 11, 2024
When PUSH is enabled with websocket transport, the redirect URL to be used
after a successfull login is not correctly computed because it is based
on the PUSH servlet mapping.
This change detects the situation and computes the correct URL.

Fixes #20575
vaadin-bot added a commit that referenced this pull request Dec 11, 2024
… 24.4) (#20678)

* fix: fix redirect URL for PUSH with websocket transport (#20666)

When PUSH is enabled with websocket transport, the redirect URL to be used
after a successfull login is not correctly computed because it is based
on the PUSH servlet mapping.
This change detects the situation and computes the correct URL.

Fixes #20575

* fix version

---------

Co-authored-by: Marco Collovati <[email protected]>
vaadin-bot added a commit that referenced this pull request Dec 11, 2024
… 24.6) (#20676)

* fix: fix redirect URL for PUSH with websocket transport (#20666)

When PUSH is enabled with websocket transport, the redirect URL to be used
after a successfull login is not correctly computed because it is based
on the PUSH servlet mapping.
This change detects the situation and computes the correct URL.

Fixes #20575

* fix version

---------

Co-authored-by: Marco Collovati <[email protected]>
vaadin-bot added a commit that referenced this pull request Dec 11, 2024
… 24.5) (#20677)

* fix: fix redirect URL for PUSH with websocket transport (#20666)

When PUSH is enabled with websocket transport, the redirect URL to be used
after a successfull login is not correctly computed because it is based
on the PUSH servlet mapping.
This change detects the situation and computes the correct URL.

Fixes #20575

* fix version

---------

Co-authored-by: Marco Collovati <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Wrong redirect after authentication when PUSH transport is WEBSOCKET
3 participants