Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

This Works To Disable Browser Back Button After Session Timeout

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    This Works To Disable Browser Back Button After Session Timeout

    I wanted to expand on Carol's code which counts down to a session timeout (See here https://forum.alphasoftware.com/show...pired-question

    However, after the session expires and redirects to the login page, I did not want the user to click the back button to get back into the application without logging in again.
    I tried some of the suggestions on the forum like this:
    Code:
    <%a5
    Response.Headers.Add("Pragma: no-cache","Cache-Control: private, max-age=0, must-revalidate, no-store")
    %>
    But this did not work for me at all.

    After digging into it some more, I came across this piece of code which does work in all browsers.
    Just put this in the head section of the main page (TabbedUI in my case);
    Code:
    <script type="text/javascript">
    function noBack(){window.history.forward();}
    noBack();
    window.onload=noBack;
    window.onpageshow=function(evt){if(evt.persisted)noBack();}
    window.onunload=function(){void(0);}
    </script>
    So now when the session expires, the user is redirected to the login page but cannot click the back button to re-establish the session.

    Stephen
    Alpha Anywhere v12.4.6.5.7 Build 9305-5711 IIS v10.0 on Windows Server 2019 Std in Hyper-V

    #2
    Re: This Works To Disable Browser Back Button After Session Timeout

    Works good! Thanks so much. These are the little things that really takes the programs to the next level and makes them professional.

    Comment


      #3
      Re: This Works To Disable Browser Back Button After Session Timeout

      Thank you very much Stephen. It works great.
      At first i put it on the index page since that is where everyone gets redirected when they logout from any part of the application, but it didn't work, so i put it in the head section of each of the pages i do not want to navigate back to. Did i do that right, or did i misunderstand you. It would be nice to just have to put it on one page.
      J.R.
      Epigate Software, LLC.

      [email protected]
      http://www.epigate.com
      sigpic

      Comment


        #4
        Re: This Works To Disable Browser Back Button After Session Timeout

        Hmm, in my case I am using a TabbedUI so I really only have one home page and that's where I have the code.
        When users logout or their session expires, I have them redirecting to the Login page. If they click the browser back button they can't get to the Home page where the code resides.
        So, I'm guessing it might need to be on each page you need to prevent this unfortunately.

        Is that vague enough of an answer? :)
        Stephen
        Alpha Anywhere v12.4.6.5.7 Build 9305-5711 IIS v10.0 on Windows Server 2019 Std in Hyper-V

        Comment


          #5
          Re: This Works To Disable Browser Back Button After Session Timeout

          Thank you Stephen, that explains it well enough. I am so glad to find a solution to this. Appreciate your time.

          -J.R.
          J.R.
          Epigate Software, LLC.

          [email protected]
          http://www.epigate.com
          sigpic

          Comment


            #6
            Re: This Works To Disable Browser Back Button After Session Timeout

            As I pointed out in J.R.'s related post:

            Originally posted by waldhorn View Post
            Regrettably, resorting to client-side JavaScript to disable the browser's back button is a band-aid on what appears to be a server-side bug. It's trivial to surreptitiously disable a specific client-side inline JavaScript...
            I'm hoping that Alpha takes care of their session leak bug and goes on develop a more robust client-side cache-handling solution.
            Last edited by waldhorn; July 11, 2012, 02:33 PM. Reason: De-emphasize bad assertion

            Comment


              #7
              Re: This Works To Disable Browser Back Button After Session Timeout

              Mark,

              Thanks for pointing that out. I wasn't aware of the points you raised. Let's hope Alpha responds to these concerns!

              Stephen
              Alpha Anywhere v12.4.6.5.7 Build 9305-5711 IIS v10.0 on Windows Server 2019 Std in Hyper-V

              Comment


                #8
                Re: This Works To Disable Browser Back Button After Session Timeout

                Originally posted by waldhorn View Post
                As I pointed out in J.R.'s related post:


                I'm hoping that Alpha takes care of thir session leak bug and goes on develop a more robust client-side cache-handling solution.
                As explained in the linked thread, there is no session leak. Unfortunately Alpha cannot automagically determine the "best" caching approach for all applications universally, so there is still work to be done by the application developer in this regard.

                Lenny Forziati
                Vice President, Internet Products and Technical Services
                Alpha Software Corporation

                Comment

                Working...
                X