Best practices regarding query strings and actions

2001-10-03 Thread chiji nwankwo
Hi, Is there a recommended way tomap query strings to actions so that their values are not displayed in the address bar. eg http://www.test.com/do/getClipper?action=searchpageNumber=12 Thanks ChijiGet your FREE download of MSN Explorer at http://explorer.msn.com

Re: Best practices regarding query strings and actions

2001-10-03 Thread Ted Husted
You could shorten the query string somewhat, and end up with something like http://www.test.com/do/getClipperSearch?pageNumber=12 but you can't eliminate it without using a form, and sending the parameters by POST rather than GET. This is just how HTTP works, and there's not much to be done

Re: Best practices regarding query strings and actions

2001-10-03 Thread Mike Bridge
It's too bad there isn't a way to do that. When one of the goals is to get some dynamic pages listed in search engines (which is a pretty common request), it would be nice to be able to construct a dynamic url like this in struts:

Re: Best practices regarding query strings and actions

2001-10-03 Thread Ted Husted
Well, that's a different question ;-) Another approach would be to use urls like, http://www.test.com/do/getClipper/search/action%3dsearch/pageNumber%3d12/ where the part after the search is passed as the query string as extra information. I'm told this would make some proxy servers happier

Re: Best practices regarding query strings and actions

2001-10-03 Thread Mike Bridge
I gave that a shot just now on the struts build from yesterday, with: http://www.test.com:8080/mywebapp/do/getClipper/test and I get the same error that is described in the url http://www.mail-archive.com/struts-user@jakarta.apache.org/msg12716.html: Error: 400 Location:

Re: Best practices regarding query strings and actions

2001-10-03 Thread Ted Husted
I never understood why it would work in the first place. I'm sure the ActionServlet is getting the extra information, but it's trying to match the URI against one of the mappings defined in the config file. So I think we would have to change the way the controller looks up the URI's, and deal