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
Devcon 2020 Goes Virtual! LEARN MORE >

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

No redirection on session expiration

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    No redirection on session expiration

    I am using App Server Ver. 10.

    When a session times out, I need to advise the user what has happened and direct them to the log-in page so they can sign back in.

    Right now, the only indication that something is wrong is the forms are confused because the session variables are gone.

    How do I let them know what's going on?
    Tags: None
    #2
    Re: No redirection on session expiration

    I have been thinking about the same thing and the only thing I have come up with is to check for the session variables in a5 code on the a5w page like so.

    if .not. eval_valid("session.__protected__vloginid")
    A5WS_LogoutUser()
    response.redirect("loginpg.a5w")
    end
    end if

    The problem is that I think this would have to be on every page the user could call up since you do not what page they were sitting on when their session timed out. And then they would only get redirected when they try to access another page. I am working in ver 9 but the problem seems to be the same. I look forward to seeing better ideas.
    Irwin

    Comment

      #3
      Re: No redirection on session expiration

      In my application, the main menu is the only object that is always open, no matter what page I'm on. Would it make sense to place your suggested code there?

      Comment

        #4
        Re: No redirection on session expiration

        Also, what event drives the eval_valid code?

        Comment

          #5
          Re: No redirection on session expiration

          I'm doubt it. Suppose your main menu (menu.a5w) has two selections which request page1.a5w and page2.a5w. When the user makes a selection on the main menu then of course menu.a5w is not requested, but one of the other pages is. So the test has to be executed in both page1.a5w and page2.a5w. I have tested the code (but only a little) and it did work. That is, I do not request any pages for 15 or 20 minutes (so the session expires) then I request a page with the test included and it does send me back to the login page. If I request a page without the test the page loads but the invalid session variables generates errors. So the test has to be in the target page not the page loaded before the time out. Some how I think there must be a better solution.

          I put the code in the target a5w page, right at the top.

          Code:
          <html><head>
<%a5
if .not. eval_valid("session.__protected__vloginid")
	A5WS_LogoutUser()
	response.redirect("loginpg.a5w")
	end
end if
%>
          � rest of the page

          So when the page is loaded, the test is called. The extra end is there to stop the execution of the rest of the page. I am writing this now from memory so maybe the placement is not exact and maybe after the <body> tag but when I can I will run the test again. Try it and see.
          Irwin

          Comment

            #6
            Re: No redirection on session expiration

            Set the login expiration policy to "Expires when current session expires", check "Enable component security for 'virtual pages'" (explained here and here), set security on all components, and the security system will automatically redirect the user to the login page when they make any request to the server and the session has expired.

            Pages that don't require login will require checking for the existence of a session variable at the start of the page as suggested. Don't use the session variable for the user identifier field (ulink) as it always exists.

            Comment

              #7
              Re: No redirection on session expiration

              That worked nicely Jerry.
              I had the login set to "Expires when current session expires" but I was not enforcing security on my pages and components. Users can have full access once they get inside so I didn't think it mattered. I learned something and that�s always a good thing.
              Thank you�

              Comment

              Previous template Next
              Working...
              X