Ends in:
1 DAY
11 HRS
8 MIN
5 SEC
Ends in:
1 D
11 H
8 M
5 S
Open Closed

Bug & Issue on version 5.1.3 #2709


User avatar
0
EneaManga created

Hello, When HttpErrorComponent is called during errors, the component template has a "Go Back" hyperlink that doesn't work. It references a javascript:void(0) method instead of redirecting the user to the previous route.

  • ABP Framework version: v5.1.3
  • UI type: Angular
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): yes
  • Exception message and stack trace:
  • Steps to reproduce the issue:" Simply reach the Error template and try the links.

3 Answer(s)
  • User Avatar
    0
    EneaManga created

    Updating the ticket to include that the Homepage redirect button also has issues on very specific hard to replicate cases.

    After some further investigation, the error 401 page that appears after the organic unauthorized happens seems to be working as expected just like the other Errors. However error 401 also gets thrown other times and behaves very differently.

    During its normal behavior error 401 Go To Homepage button redirects the user to the login screen. However in the other cases the button calls 5 random http requests on every click of this button. This error 401 case cannot be replicated as easily as the normal one can.

    This is an unwanted behavior as the user should not lose authorized status during this time.

  • User Avatar
    0
    mahmut.gundogdu created

    Hi EneaManga,

    When the error appears, HttpError Component is added to DOM. (just like a modal). It covers all the pages. The Default HttpErrorComponent has two buttons. "Go to home" button/link redirect to '/' with routeLink directive and destroy itself. "Go Back" button is called destroy method and remove the "HttpErrorComponent"

    If there is a page in dom, it is shown. This is the behavior of HttpErrorComponent. If any page/component doesn't exist in dom, the user clicks to go back; the page is shown blank. It will be fixed. I have opened a task for that. It will release 5.3.

    But I didn't understand why the user lost auth status. And I can't see like that. If you don't want to wait for 5.3 you can change the HttpErrorCompoent with your own custom component.

    HttpError component defined in AppConfig. You can change it.

  • User Avatar
    0
    EneaManga created

    Thank you for your answer. I will be waiting for the new version to determine whether the issue still persists or not and advance from that point. Best Regards, Enea Manga

Made with ❤️ on ABP v9.1.0-preview. Updated on December 05, 2024, 12:19