-
Notifications
You must be signed in to change notification settings - Fork 164
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
Upgrade from 3.6.2 to 3.7.0 - Redirecting to 404.html #246
Comments
I just published 3.7.1 to correct the faulty logic. Let me know whether it fixes the issue. |
upgraded to 3.7.1; it works almost :) |
It's an expected debug message. The wording may change in the future since it's misleading if you're not using dotNetify routing, but shouldn't be a problem for closing this issue. Thanks! |
Thank you for the quick turnaround.
Yes, I can live with that erroneous debug message.
…On Mon, May 18, 2020, 10:17 AM Dicky Suryadi ***@***.***> wrote:
It's an expected debug message. The wording may change in the future since
it's misleading if you're not using dotNetify routing, but shouldn't be a
problem for closing this issue. Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#246 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAF4Y3GIRJO25FNTZIZBUGLRSFGQBANCNFSM4NDXBZTA>
.
|
We have been using DotNetify since 3.3.1.
Without changing any of our code and after upgrading from 3.6.2 to 3.7.0, dotNetify will auto redirect to 404.html.
However, If I add "dotnetify.react.router.urlPath = null;" before calling connect, everything works as before.
I believe the issue is in dotnetify-vm-router.ts line # 88
Please assist.....
-- our pre-connect setup --
import dotnetify from 'dotnetify';
dotnetify.hubServerUrl = document.location.origin + '/' + document.location.pathname.split('/')[1];;
dotnetify.debug = (!process.env.NODE_ENV || process.env.NODE_ENV === 'development');
//added to prevent auto redirect to 404.html
dotnetify.react.router.urlPath = null;
The text was updated successfully, but these errors were encountered: