A: 

Hi,

first of all, if you are using MVC forms, than use

<%= Html.DisplayFor(m => m.Id2) %>

instead of manually draw them.

And there is no possibility for a Html form to directly put the values in the URL. they either put it in the POST (Header variables) or GET (query strings). therefore, if you want the behaviour you have to do the Javascript by yourself.

and, btw, this only works, if your route accepts the value.

context.MapRoute("{controller}/{action}/{id}/{id2}")
cRichter
+1  A: 

Personally I'd follow the PRG pattern here.

The users fills in your form which then gets POSTed back to the server, you perform any operations on the data you need and then redirect the user via a GET to the appropriate place (redirect to action, route etc).

This has a couple of benefits for you. The first and most obvious is that the user can now refresh their destination page etc without the horrible "Refreshing this page will post bla bla back to the server" message.

The second benefit for you is that you can now redirect your user to the URL you prefer. In your case you'll build up the URL you're going to be redirecting too and then send them on their way. i.e. http://localhost/Home/Listing/test1/test2

Jamie Dixon