Every time we do a search we point the front end of our application to
https://search.childrensoncologygroup.org. We do this behind the
scenes, so this url is never exposed. Everything displays under
http://members.childrensoncologygroup.org.
Now, if I pass all the parameters of a search under something like
this:
https://search.childrensoncologygroup.org/search?q=1991&btnG=Search&e... , a user can actually see all the records, and we don't want this. I
know that if they click the links they will have to login to the
member website to see the document, but we want to make sure that
users DO NOT get to this url.
> Every time we do a search we point the front end of our application to > https://search.childrensoncologygroup.org. We do this behind the > scenes, so this url is never exposed. Everything displays under > http://members.childrensoncologygroup.org. > Now, if I pass all the parameters of a search under something like > this: > https://search.childrensoncologygroup.org/search?q=1991&btnG=Search&e... > , a user can actually see all the records, and we don't want this. I > know that if they click the links they will have to login to the > member website to see the document, but we want to make sure that > users DO NOT get to this url.
|
