Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <h1>Useful Technical Details</h1> <h2>Removing/Preventing Back Button Click History</h2> <p>You can allow the user to browse throughout a webpage without building up a history trail on the back button by having them click exclusively on <code>javascript:</code> links. <strong><em>This would still not remove any of the visited websites from their full browser history, so it's not a full solution.</em></strong></p> <p>Here's an example HTML JavaScript link:</p> <pre><code>&lt;a href="javascript:document.location.replace('http://www.google.com/#q=something+innocuous');"&gt;CLICK HERE TO ESCAPE!&lt;/a&gt; </code></pre> <p>If this is acceptable, you could build an inoffensive homepage from which the user could access the site that would use JavaScript to send them to the real website. Every link on that new website would have to be a javascript link. Disadvantages of this would be that they would no longer be able to use the back button to navigate and that JavaScript is 100% required for the site to function.</p> <h3>Sanitized History</h3> <p>Make sure you have inoffensive titles and icons for any pages in the site so if the user does not delete their browser history they will not grab the attention of the third party.</p> <h2>Preventing Access to Protected Content</h2> <p>One option you have is to disguise your website as something else by having the user log in before they are allowed to access any of the content. You could save their session/login data in such a way that it is cleared if they hit an escape button it is erased or reset. As part of the login page, you could give users an alternate password to type in that would redirect them to fake content if their abuser becomes suspicious enough to demand they log in.</p> <p>The session/login information should never save between browser sessions and always have a short expiration period, to further reduce the chances of the abuser gaining access to the website.</p> <h1>Disguising the Site</h1> <h2>Considerations</h2> <p>If you choose to disguise the site either on the homepage or behind a "fake" login, be very careful to choose something that makes sense and would not arouse suspicion or interest. You don't want the fake page to be some sort of game or anything that might pique the third party's interest. </p> <p>You also don't want it to look so boring or mundane that the original user would be hard-pressed to explain their possibly frequent visits. It shouldn't be anything so specific that the third party would think twice about the original user visiting it though. For example, it might be suspicious if someone who does not enjoy the great outdoors were to be visiting a page on mountain biking.</p> <p>It also can't do something like just redirect them to Google without explaining the fact that they had to log in to access it.</p> <h1>General Advice</h1> <h2>Private Browsing</h2> <p>Multiple sources have suggested either educating your target audience in how to use IE's <a href="http://windows.microsoft.com/en-us/internet-explorer/products/ie-9/features/in-private" rel="noreferrer">InPrivate Browsing mode</a>, Firefox's <a href="http://support.mozilla.org/en-US/kb/private-browsing-browse-web-without-saving-info" rel="noreferrer">Private Browsing mode</a>, or Chrome's <a href="https://support.google.com/chrome/answer/95464?hl=en" rel="noreferrer">Incognito mode</a>.</p> <p>There unfortunately does not appear to be a way to prevent the browser from keeping the current page in its browsing history through JavaScript. It's possible there might be some sort of plug-in or third-party control which would enable this, but it's probably just easier to get your users to use a private browsing mode.</p> <h2>Clearing History</h2> <p>Clearing a user's web history would not be possible since browsers restrict websites from accessing or altering data on the user's computer directly. Since the user's browser history is part of this data it would be a security issue if any website could clear the history.</p> <p>You should provide instructions to your users for pruning or clearing their browser history, whether on the website itself before they enter, or through whatever resource you showed them how to access your website.</p> <h2>Generating a Fake History</h2> <p>If you need to generate a fake list of visited websites, you can always create new tabs/windows for the users (or possibly iframes) at timed intervals with JavaScript, but the user would have to disable their popup blocker for this to take effect.</p> <h1>Further Reading</h1> <p>Here is a helpful article on creating a useful <a href="http://css-tricks.com/website-escape/" rel="noreferrer">Quick Disguised Exit From A Website</a>. This <a href="http://www.webdesignerforum.co.uk/topic/64899-hide-site-from-browser-history/" rel="noreferrer">forum thread</a> that I found it on also had some useful information, but it's likely you've already seen it.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to populate a fake browser history?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCorion
    1. USCorion
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to populate a fake browser history?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe demo is nice and simple. Thank you Corion!
      singulars
      1. PO
      1. USSebastien DErrico
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload