React Auth state and Routes . Failed to execute 'replaceState' on 'History' inside React-Router
up vote
7
down vote
favorite
Using packages
"react-router": "^4.3.1",
"react-router-dom": "^4.3.1",
App.js
class App extends Component {
constructor(props) {
super(props);
this.state = {
authState: null,
};
}
mutateAuthState = () => {
this.setState({
authState: true,
});
}
render() {
return (<Routes authState={this.state.authState} mutateAuthState={this.mutateAuthState} />)
}
}
Routes.js
class Routes extends React.Component {
render() {
return (
<React.Fragment>
<BrowserRouter >
<Switch>
<Route path="/login" exact render={ () => <Login authState={this.props.authState}
mutateAuthState={this.props.mutateAuthState}/>
} />
<Route path="/" exact render={ () => <div><a href="/login" >login</a></div> } />
</Switch>
</BrowserRouter>
</React.Fragment>
);
}
}
Login.js
class Login extends Component {
handleSubmit = async (event) => {
this.props.mutateAuthState(true)
}
render() {
switch(this.props.authState) {
case true : return (<Redirect to="" />)
default : return(
<button onClick={this.handleSubmit} >Login </button>
)
}
}
}
End result wanted - Clicking Login Button in Login.js will set the state variable authState in App.js to true.
App will rerender Routes.js since state has changed.
Inside Routes, since the url is still /login , Login component is rendered.
Inside Login, since this.props.authState is now set to true, a redirect to "/" occures.
But I am getting a DOMException in Web Console
Error: DOMException: Failed to execute 'replaceState' on 'History': A
history state object with URL 'http:' cannot be created in a document
with origin 'http://localhost:3000' and URL
'http://localhost:3000/login'.
Is this the proper architecture for Authentication in React?
reactjs react-router-dom
add a comment |
up vote
7
down vote
favorite
Using packages
"react-router": "^4.3.1",
"react-router-dom": "^4.3.1",
App.js
class App extends Component {
constructor(props) {
super(props);
this.state = {
authState: null,
};
}
mutateAuthState = () => {
this.setState({
authState: true,
});
}
render() {
return (<Routes authState={this.state.authState} mutateAuthState={this.mutateAuthState} />)
}
}
Routes.js
class Routes extends React.Component {
render() {
return (
<React.Fragment>
<BrowserRouter >
<Switch>
<Route path="/login" exact render={ () => <Login authState={this.props.authState}
mutateAuthState={this.props.mutateAuthState}/>
} />
<Route path="/" exact render={ () => <div><a href="/login" >login</a></div> } />
</Switch>
</BrowserRouter>
</React.Fragment>
);
}
}
Login.js
class Login extends Component {
handleSubmit = async (event) => {
this.props.mutateAuthState(true)
}
render() {
switch(this.props.authState) {
case true : return (<Redirect to="" />)
default : return(
<button onClick={this.handleSubmit} >Login </button>
)
}
}
}
End result wanted - Clicking Login Button in Login.js will set the state variable authState in App.js to true.
App will rerender Routes.js since state has changed.
Inside Routes, since the url is still /login , Login component is rendered.
Inside Login, since this.props.authState is now set to true, a redirect to "/" occures.
But I am getting a DOMException in Web Console
Error: DOMException: Failed to execute 'replaceState' on 'History': A
history state object with URL 'http:' cannot be created in a document
with origin 'http://localhost:3000' and URL
'http://localhost:3000/login'.
Is this the proper architecture for Authentication in React?
reactjs react-router-dom
add a comment |
up vote
7
down vote
favorite
up vote
7
down vote
favorite
Using packages
"react-router": "^4.3.1",
"react-router-dom": "^4.3.1",
App.js
class App extends Component {
constructor(props) {
super(props);
this.state = {
authState: null,
};
}
mutateAuthState = () => {
this.setState({
authState: true,
});
}
render() {
return (<Routes authState={this.state.authState} mutateAuthState={this.mutateAuthState} />)
}
}
Routes.js
class Routes extends React.Component {
render() {
return (
<React.Fragment>
<BrowserRouter >
<Switch>
<Route path="/login" exact render={ () => <Login authState={this.props.authState}
mutateAuthState={this.props.mutateAuthState}/>
} />
<Route path="/" exact render={ () => <div><a href="/login" >login</a></div> } />
</Switch>
</BrowserRouter>
</React.Fragment>
);
}
}
Login.js
class Login extends Component {
handleSubmit = async (event) => {
this.props.mutateAuthState(true)
}
render() {
switch(this.props.authState) {
case true : return (<Redirect to="" />)
default : return(
<button onClick={this.handleSubmit} >Login </button>
)
}
}
}
End result wanted - Clicking Login Button in Login.js will set the state variable authState in App.js to true.
App will rerender Routes.js since state has changed.
Inside Routes, since the url is still /login , Login component is rendered.
Inside Login, since this.props.authState is now set to true, a redirect to "/" occures.
But I am getting a DOMException in Web Console
Error: DOMException: Failed to execute 'replaceState' on 'History': A
history state object with URL 'http:' cannot be created in a document
with origin 'http://localhost:3000' and URL
'http://localhost:3000/login'.
Is this the proper architecture for Authentication in React?
reactjs react-router-dom
Using packages
"react-router": "^4.3.1",
"react-router-dom": "^4.3.1",
App.js
class App extends Component {
constructor(props) {
super(props);
this.state = {
authState: null,
};
}
mutateAuthState = () => {
this.setState({
authState: true,
});
}
render() {
return (<Routes authState={this.state.authState} mutateAuthState={this.mutateAuthState} />)
}
}
Routes.js
class Routes extends React.Component {
render() {
return (
<React.Fragment>
<BrowserRouter >
<Switch>
<Route path="/login" exact render={ () => <Login authState={this.props.authState}
mutateAuthState={this.props.mutateAuthState}/>
} />
<Route path="/" exact render={ () => <div><a href="/login" >login</a></div> } />
</Switch>
</BrowserRouter>
</React.Fragment>
);
}
}
Login.js
class Login extends Component {
handleSubmit = async (event) => {
this.props.mutateAuthState(true)
}
render() {
switch(this.props.authState) {
case true : return (<Redirect to="" />)
default : return(
<button onClick={this.handleSubmit} >Login </button>
)
}
}
}
End result wanted - Clicking Login Button in Login.js will set the state variable authState in App.js to true.
App will rerender Routes.js since state has changed.
Inside Routes, since the url is still /login , Login component is rendered.
Inside Login, since this.props.authState is now set to true, a redirect to "/" occures.
But I am getting a DOMException in Web Console
Error: DOMException: Failed to execute 'replaceState' on 'History': A
history state object with URL 'http:' cannot be created in a document
with origin 'http://localhost:3000' and URL
'http://localhost:3000/login'.
Is this the proper architecture for Authentication in React?
reactjs react-router-dom
reactjs react-router-dom
edited Nov 12 at 0:10
asked Oct 25 at 3:23
Shorn Jacob
3063516
3063516
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
5
down vote
Two things that I can see.
Shouldn't you be redirecting to forward slash and not backslash?
aka change <Redirect to="" />
to <Redirect to="/" />
Second thing is you probably need to upgrade your version of react-router. The issue is your redirect is trying to go back to home, but there is a bug when redirecting to the /
route.
Version 4.6.1
should correctly redirect for you.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
Two things that I can see.
Shouldn't you be redirecting to forward slash and not backslash?
aka change <Redirect to="" />
to <Redirect to="/" />
Second thing is you probably need to upgrade your version of react-router. The issue is your redirect is trying to go back to home, but there is a bug when redirecting to the /
route.
Version 4.6.1
should correctly redirect for you.
add a comment |
up vote
5
down vote
Two things that I can see.
Shouldn't you be redirecting to forward slash and not backslash?
aka change <Redirect to="" />
to <Redirect to="/" />
Second thing is you probably need to upgrade your version of react-router. The issue is your redirect is trying to go back to home, but there is a bug when redirecting to the /
route.
Version 4.6.1
should correctly redirect for you.
add a comment |
up vote
5
down vote
up vote
5
down vote
Two things that I can see.
Shouldn't you be redirecting to forward slash and not backslash?
aka change <Redirect to="" />
to <Redirect to="/" />
Second thing is you probably need to upgrade your version of react-router. The issue is your redirect is trying to go back to home, but there is a bug when redirecting to the /
route.
Version 4.6.1
should correctly redirect for you.
Two things that I can see.
Shouldn't you be redirecting to forward slash and not backslash?
aka change <Redirect to="" />
to <Redirect to="/" />
Second thing is you probably need to upgrade your version of react-router. The issue is your redirect is trying to go back to home, but there is a bug when redirecting to the /
route.
Version 4.6.1
should correctly redirect for you.
edited Nov 12 at 4:40
answered Nov 12 at 0:34
John Ruddell
15.9k43158
15.9k43158
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52980882%2freact-auth-state-and-routes-failed-to-execute-replacestate-on-history-insi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown