Forum Moderators: phranque

Message Too Old, No Replies

Hide additional paths in my url

         

rasheed

10:13 am on Oct 31, 2004 (gmt 0)

10+ Year Member



I'm asking if their is a way to hide any additional paths in my url website and always appears in browser my domain..ie..if some one request page [abc.com...] get it put nothing shows in the browser of these "servlet/runHXML?action=WS_Login.xsp"...only appears [abc.com....]
I have apache2.0.52...

Rasheed

jdMorgan

9:42 pm on Nov 3, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



rasheed,

Welcome to WebmasterWorld!

You can change the form of these URLs, but each resource on your server must be uniquely-identified in order for a browsser to request it. Therefore, multiple resources can't have the same URL.

I'm not sure I understood your question, so I hope this helps.

Jim

rasheed

9:20 am on Nov 6, 2004 (gmt 0)

10+ Year Member



What I asked exactly is to hide any url other than the my domain name (www.abc.com) wherever the visitor go inside my website (mask URL) . For security reasons I don't want him to see the full path of the pages.

jdMorgan

2:57 pm on Nov 6, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



You could do this using session ID cookies to track the visitor's current "location" inside your site. This will require you to have a script and database to track the state of each visitor over time. Flushing the database of outdated entries becomes a problem -- flush too soon and you lose visitors who were called away for a few hours, wait too long and your database becomes bloated.

You will also need to implement the function of the "back" button manually; Since the browser won't be aware of any changes in the URL, the regular back button won't work.

This is a very "user-unfriendly" method, difficult to debug, and prone to major problems. Be sure there are no friendlier and easier techniques you could use to achieve your actual needs before heading down this path. For example, using password-protection and a cookie to remember the authorization-state would be simpler. If your site is dynamically-generated, modifying the scripts to add a date-related or pseudo-random component to the URLs would also be easier.

This is an advanced subject, and I can offer little more than the above comments.

Jim