-
Notifications
You must be signed in to change notification settings - Fork 92
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
Add options for error pages #12
Comments
Hi @TristanPct , We are currently working on the v2.0 of Highway... We have add a new method called So I would say that since the Cheers, |
👍 This method could be usefull, for this case or others. But with this technique the browser load the error page twice (for the Perhaps a method or parameter in the |
@TristanPct I understand what you mean and we'll look into a cleaner solution as soon as possible. |
@TristanPct We juste released the v2.0.0 of Highway that will fix your issue. Since we cannot predict that there will be an error or that an error page is provided we have to hard reload the page as soon as the Best regards, |
Hello, it's me again 😄
For the moment when Highway encounter an error page (404, 500...) it sends the NAVIGATE_ERROR event but doesn't try to load the page (event if this page have a
router-view
).Is it planned to add an option to load error pages likes other pages ?
For the moment an alternative is to tell the error page to have an HTTP 200 code rather than error code if
X-Requested-With: Highway
header is present.The text was updated successfully, but these errors were encountered: