React Router not found page showing up on all paths












0















I'm experimenting with a bit of React Routing, and I experienced a problem when I tried to make an error page, which occurs each time the users gets a 404 error, which prompts a message:



import React from "react";

const Error = props => {
return(
<div>
<p>
Path does not exist!
</p>
</div>
)

}

export default Error;


I wrapped all my paths, with a switch statement, to only make it apply to the absolute paths.



class App extends Component {

render() {
return (
<BrowserRouter>
<Switch>
<div>
<Route exact path="/" component={Home} />
<Route exact path="/about" component={About} />
<Route path="*" exact component={Error} />
</div>
</Switch>
</BrowserRouter>
);
}
}


but know whenever I access a path, the Error component shows up.



But I since I wrap in a Switch component, and use exact, shouldn't the Error component only show up, whenever another path does not exist?










share|improve this question























  • shot in the dark but have you tried removing the div? Also the path="*" is not needed you do not have to supply the path param if you always want it to show.

    – Eric Hasselbring
    Nov 15 '18 at 19:10
















0















I'm experimenting with a bit of React Routing, and I experienced a problem when I tried to make an error page, which occurs each time the users gets a 404 error, which prompts a message:



import React from "react";

const Error = props => {
return(
<div>
<p>
Path does not exist!
</p>
</div>
)

}

export default Error;


I wrapped all my paths, with a switch statement, to only make it apply to the absolute paths.



class App extends Component {

render() {
return (
<BrowserRouter>
<Switch>
<div>
<Route exact path="/" component={Home} />
<Route exact path="/about" component={About} />
<Route path="*" exact component={Error} />
</div>
</Switch>
</BrowserRouter>
);
}
}


but know whenever I access a path, the Error component shows up.



But I since I wrap in a Switch component, and use exact, shouldn't the Error component only show up, whenever another path does not exist?










share|improve this question























  • shot in the dark but have you tried removing the div? Also the path="*" is not needed you do not have to supply the path param if you always want it to show.

    – Eric Hasselbring
    Nov 15 '18 at 19:10














0












0








0








I'm experimenting with a bit of React Routing, and I experienced a problem when I tried to make an error page, which occurs each time the users gets a 404 error, which prompts a message:



import React from "react";

const Error = props => {
return(
<div>
<p>
Path does not exist!
</p>
</div>
)

}

export default Error;


I wrapped all my paths, with a switch statement, to only make it apply to the absolute paths.



class App extends Component {

render() {
return (
<BrowserRouter>
<Switch>
<div>
<Route exact path="/" component={Home} />
<Route exact path="/about" component={About} />
<Route path="*" exact component={Error} />
</div>
</Switch>
</BrowserRouter>
);
}
}


but know whenever I access a path, the Error component shows up.



But I since I wrap in a Switch component, and use exact, shouldn't the Error component only show up, whenever another path does not exist?










share|improve this question














I'm experimenting with a bit of React Routing, and I experienced a problem when I tried to make an error page, which occurs each time the users gets a 404 error, which prompts a message:



import React from "react";

const Error = props => {
return(
<div>
<p>
Path does not exist!
</p>
</div>
)

}

export default Error;


I wrapped all my paths, with a switch statement, to only make it apply to the absolute paths.



class App extends Component {

render() {
return (
<BrowserRouter>
<Switch>
<div>
<Route exact path="/" component={Home} />
<Route exact path="/about" component={About} />
<Route path="*" exact component={Error} />
</div>
</Switch>
</BrowserRouter>
);
}
}


but know whenever I access a path, the Error component shows up.



But I since I wrap in a Switch component, and use exact, shouldn't the Error component only show up, whenever another path does not exist?







reactjs






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 15 '18 at 18:51









baileyhaldwinbaileyhaldwin

794318




794318













  • shot in the dark but have you tried removing the div? Also the path="*" is not needed you do not have to supply the path param if you always want it to show.

    – Eric Hasselbring
    Nov 15 '18 at 19:10



















  • shot in the dark but have you tried removing the div? Also the path="*" is not needed you do not have to supply the path param if you always want it to show.

    – Eric Hasselbring
    Nov 15 '18 at 19:10

















shot in the dark but have you tried removing the div? Also the path="*" is not needed you do not have to supply the path param if you always want it to show.

– Eric Hasselbring
Nov 15 '18 at 19:10





shot in the dark but have you tried removing the div? Also the path="*" is not needed you do not have to supply the path param if you always want it to show.

– Eric Hasselbring
Nov 15 '18 at 19:10












1 Answer
1






active

oldest

votes


















1














   <Switch>
<Route exact path="/" component={Home} />
<Route exact path="/about" component={About} />
<Route component={Error} />
</Switch>


Do not add a path for error route.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53326139%2freact-router-not-found-page-showing-up-on-all-paths%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














       <Switch>
    <Route exact path="/" component={Home} />
    <Route exact path="/about" component={About} />
    <Route component={Error} />
    </Switch>


    Do not add a path for error route.






    share|improve this answer




























      1














         <Switch>
      <Route exact path="/" component={Home} />
      <Route exact path="/about" component={About} />
      <Route component={Error} />
      </Switch>


      Do not add a path for error route.






      share|improve this answer


























        1












        1








        1







           <Switch>
        <Route exact path="/" component={Home} />
        <Route exact path="/about" component={About} />
        <Route component={Error} />
        </Switch>


        Do not add a path for error route.






        share|improve this answer













           <Switch>
        <Route exact path="/" component={Home} />
        <Route exact path="/about" component={About} />
        <Route component={Error} />
        </Switch>


        Do not add a path for error route.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 15 '18 at 19:13









        OmarOmar

        1,8851722




        1,8851722
































            draft saved

            draft discarded




















































            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53326139%2freact-router-not-found-page-showing-up-on-all-paths%23new-answer', 'question_page');
            }
            );

            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







            Popular posts from this blog

            Bressuire

            Vorschmack

            Quarantine