How can I just change the get parameter without redirecting?
parent.location.search = "?after=20";
// ok that changes, but also redirect to the new page
Any solution? Or answer is no, if its no, please write big no.
views:
919answers:
5
+1
A:
Uh, no - if you change the URL parameter, your browser will load the new page.
Not necessarily... If the server returns a 204, the browser will stay on the same page.
Ates Goral
2009-09-28 17:32:20
+1
A:
You cannot alter the querystring (ie. the part that stars with the ?) without reloading the page from the server. You can however use page anchors like http://www.example.com/page.html#anchorname to affect the url without reloading a page from the server.
Asaph
2009-09-28 17:04:01
+7
A:
NO
You can come close with the anchor portion of the URL which is accessible by the hash property of the location object
parent.location.hash = "whatever value you want";
Peter Bailey
2009-09-28 17:06:17
i like the @ates-goral answer better, but its not supported by all browsers, very sadly. plus it wont be secruity risk, if someone changes the query string, its not like person is changing the complete path or domain. even if user can change the path, that dont mean its a security risk, because domain would still be same, unless its a blog site.
Basit
2009-10-27 21:52:59
I like this, but you need to be aware that the # value is never sent to the server http://stackoverflow.com/questions/774136/retrieving-anchor-link-in-url-for-asp-net
row1
2010-03-25 03:03:52
+3
A:
If your aim is to use the query string to store some state that can later be restored from a bookmark, you should use anchors instead.
However, if you must change the query string for some reason, actually there is a way. However, I don't endorse this. I'm just mentioning it for completeness.
When a server returns a 204 No Content response, most browsers won't do anything -- i.e. won't even attempt to transition to another page or even wipe the current page. What you can do is to make the backend just emit a 204 response when a request is made to the same page that was just served, with a change in the query parameters.
Ates Goral
2009-09-28 17:15:55
so this method really depend on a browser, if browser do redirect, then there is no way stopping it.. right? i can set 204 response, only if i know the draw-backs
Basit
2009-09-28 17:21:04
You can safely assume that all reasonably modern browsers behave the same way -- ie. stay on the same page.
Ates Goral
2009-09-28 17:22:04
I remember getting it to work on both Firefox and IE. You should definitely test it yourself to be sure. But again, I implore you to use anchors instead! :)
Ates Goral
2009-09-28 18:53:28
Tried this in Safari 4, it clears the query string when it receives the 204 response.
eyelidlessness
2009-10-27 17:41:54
A:
You can't do this because it would be a security risk if you could.... If pages could change the value in the URL bar, it would be easy for page put up by a phisher to change that value to appear to be a page on your bank's website.
Spike Williams
2009-10-27 17:20:03
There's a big difference between changing the query string and changing the rest of the path. If your current host name isn't fooling anyone, it's not going to fool anyone any more when you change it, especially because you can still change it and control what's output even if it does go to the server to retrieve the new URL.
eyelidlessness
2009-10-27 17:47:32
like i said below:i like the @ates-goral answer better, but its not supported by all browsers, very sadly. plus it wont be secruity risk, if someone changes the query string, its not like person is changing the complete path or domain. even if user can change the path, that dont mean its a security risk, because domain would still be same, unless its a blog site.
Basit
2009-10-27 21:53:37
I don't really think it should be up to the browser to decide what parts of the URL in the address bar its safe to change or not...that's kind of a silly minor feature for a browser to implement, and you know that it would be different between different browsers.
Spike Williams
2009-10-27 22:39:37
ya i agree, but browser should let users change the path (NOT DOMAINS), cause now days everyone prefer to do stuff using ajax and changing path is for just letting user use to share the link with other users for current page. yes i know you can do it with hash too, but its confusing for people to share link with title of different media, but they are sharing of different page, because they got that from ajax.. obviously there are some other solutions.. but ideal would be letting the domain owners change the path they own.
Basit
2009-10-28 01:12:17