How do I prevent my web application from being redirected through URL modification?

Question

0.00/5 (No votes)

See more:

Hello guys,

Let's say when I run my web application on my locahost, and the url in the broswer is like ~/Page1.

If the user changes the url from "~/Page1" to "~/Page2", they will be redirected to "~/Page2".

Is there any way for me to prevent this url modification? Since I need the user to be able to complete the required actions on Page1 before they can proceed to Page2.

Any help will be appreciated.

Thanks in advance.

Posted 27-Aug-14 20:16pm

Member 10915623

Add a Solution

Comments

Tejas Vaishnav 16-Dec-14 2:00am

Is my answer solve your question then mark my answer as solution and don't forget to rate it.

Member 10915623 16-Dec-14 21:24pm

Thanks for the solution, nearly forgot about marking it

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Tejas Vaishnav · Accepted Answer · 2014-08-27T20:29:00

=> Do one thing, you can create some session which is only contains valid data when user has finished steps over first page.

=> check that session in your second page load event, if that session is valid then allow user to access second page, other wise redirect to first page again.

the same mechanism like we have checked user authentication, if user is not logged in then we redirect him to login page, or if logged in then can access other page. you can create same for your solution.