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

Session Variables - __protected__

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

    Session Variables - __protected__

    The need to have __protected__ at the beginning of session variables went away some time ago. With today's pre-release, however, it seems to be back. At least for this specific usage case. This brings me to my question: Outside of this pre-release functionality are "__protected__" session vars handled any differently overall within Alpha?

    Ashampoo_Snap_Thursday, December 7, 2017_07h49m56s_003_.png
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Programmatic-Technologies.com
    Independent Developer & Consultant​​

    #2
    Re: Session Variables - __protected__

    I don't think there's any difference. I have an app that was started well before the __protected__ change and still have a couple of those variables in use - nothing about them has changed.

    Note that session.__protected__activeLanguage is the other one (another one?) that requires this syntax.
    -Steve
    sigpic

    Comment


      #3
      Re: Session Variables - __protected__

      Originally posted by mikeallenbrown View Post
      The need to have __protected__ at the beginning of session variables went away some time ago. With today's pre-release, however, it seems to be back. At least for this specific usage case. This brings me to my question: Outside of this pre-release functionality are "__protected__" session vars handled any differently overall within Alpha?

      [ATTACH=CONFIG]44317[/ATTACH]
      I'd bet it's more of a case that existing code in Alpha requires a naming convention of "__protected__<name>". It's much safer and easier to require that naming convention than change older, existing code in a thousand places. It's not that protected session variables are back... it's just the name which must be used in this case.

      While the use of that naming convention in this case is required, I certainly wouldn't go anywhere near using "__protected__" for anything new. I'd guess there's only a handful of people within Alpha than can answer the question about how "__protected__" is actually handled.

      Comment


        #4
        Re: Session Variables - __protected__

        If you try to change any session variables from client side you get error:

        Code:
        400 Bad Request
        Unsafe Session variable syntax. Session variables cannot be created or assigned from either the Query String or POST body.
        Same error if you try to make your own session variables from client side.

        So protection for session variables seems to be working.
        Request variables you can of course create from client side and tamper them (do not know how Alpha Grid of UX protects Request variables).
        Last edited by kkfin; 12-07-2017, 03:09 PM.

        Comment


          #5
          Re: Session Variables - __protected__

          If you try to change any session variables from client side you get error:
          You've not shown HOW you're trying to change a session variable on the client-side... there is no mechanism for doing this.
          Last edited by Davidk; 12-07-2017, 04:08 PM.

          Comment


            #6
            Re: Session Variables - __protected__

            Originally posted by Davidk View Post
            I'd bet it's more of a case that existing code in Alpha requires a naming convention of "__protected__<name>". It's much safer and easier to require that naming convention than change older, existing code in a thousand places.
            Makes sense. Thanks.
            Mike Brown - Contact Me
            Programmatic Technologies, LLC
            Programmatic-Technologies.com
            Independent Developer & Consultant​​

            Comment


              #7
              Re: Session Variables - __protected__

              Originally posted by Davidk View Post
              You've not shown HOW you're trying to change a session variable on the client-side... there is no mechanism for doing this.
              Hi David,

              I understand totally your concern . And I am happy to tell you that server handles the session variables.

              But you can pass them to the server from client side. Hope better English nuw But server does not anymore accept them form client side as the error message tells. Things were different in past.

              Comment

              Working...
              X