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

Cookie syntax

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

    Cookie syntax

    We've seen in a v11 thread that we should be able to set a cookie like this:

    Code:
    dim NewCookie as System::Web::HttpCookie = new System::Web::HttpCookie("cart_id")
    NewCookie.value = cart_id
    NewCookie.expires = now() + (12000)
    response.cookies.add(NewCookie)
    So, based on Steve Woods' example, shouldn't I expect something other than this in Interactive?:

    Code:
    dim NewCookie as System::Web::HttpCookie = new System::Web::HttpCookie("cart_id")
    ?cart_id
    ERROR: Variable "cart_id" not found.
    When I try this on the web page, I get:

    500 Internal Server Error

    Script Error
    Error:Script:" /MyPage.a5w" line:82
    NewCookie.Value = cart_id
    Variable "cart_id" not found.
    -Steve
    sigpic

    #2
    Re: Cookie syntax

    Originally posted by Steve Workings View Post
    We've seen in a v11 thread that we should be able to set a cookie like this:

    Code:
    dim NewCookie as System::Web::HttpCookie = new System::Web::HttpCookie("cart_id")
    NewCookie.value = cart_id
    NewCookie.expires = now() + (12000)
    response.cookies.add(NewCookie)
    So, based on Steve Woods' example, shouldn't I expect something other than this in Interactive?:

    Code:
    dim NewCookie as System::Web::HttpCookie = new System::Web::HttpCookie("cart_id")
    ?cart_id
    ERROR: Variable "cart_id" not found.
    When I try this on the web page, I get:
    Steve,
    try this:

    <%a5

    dim cart_id as C = "100"
    dim NewCookie as System::Web::HttpCookie = new System::Web::HttpCookie("cookie2")
    'set the value (data to be stored in the cookie
    NewCookie.Value = cart_id
    ' make this an "HTTP-Only" cookie
    NewCookie.HttpOnly = .f.

    Response.Cookies.Add(NewCookie)


    if eval_valid("request.cookies.cookie2") then
    ? "<P>The cookie2 has value "+request.cookies.cookie2+"</P>"


    end if

    %>

    Comment


      #3
      Re: Cookie syntax

      Steve,

      What is missing from your code is setting a value for the cookie. I dont know where you clipped my example, but somewhere above your snippet, I would have set a value for "cart_id". What makes it confusing is that, in my original example, I was generating a local variable named cart_id, then creating a cookie also named cart_id and setting its value to the local variable. A better example is below. In this example, the value for the cookie is generated directly, without redundantly setting any local variable.

      dim NewCookie as system::Web::HttpCookie = new System::Web::HttpCookie("cart_id")
      NewCookie.value = api_uuidcreate()
      NewCookie.expires = now() + (12000)
      response.cookies.add(NewCookie)
      ?"My cookie is: " + request.cookies.cart_id
      'Or just cart_id, but request.cookies.cart_id is safer
      Of course, if your cookie already exists, you generally don't want to create a new value, so you would bound the above code with an IF statement and only generate a new cookie value if it did not already have a value.
      Steve Wood
      See my profile on IADN

      Comment


        #4
        Re: Cookie syntax

        Thanks Steve & Eric. So what's wrong with this below? It's not creating a cookie:

        Code:
        	dim NewCookie as System::Web::HttpCookie = new System::Web::HttpCookie("_My_cookie")
        	NewCookie.Value= api_uuidcreate()
        	NewCookie.Expires = now() + (12000)
        	NewCookie.Name = "_My_cookie"
        	Response.Cookies.Add(NewCookie)
        -Steve
        sigpic

        Comment


          #5
          Re: Cookie syntax

          Your code does create a cookie. See the attached image using your code. Its not going to work in Interactive because that is not a browser.
          Attached Files
          Steve Wood
          See my profile on IADN

          Comment


            #6
            Re: Cookie syntax

            Alright, lemme explain what I'm trying to do.

            I have a connection to an API. When the first user logs in to OERCA, I also log that user --- with that username -- into the API.

            The API stores 4 cookies into the browser. I can see them in Chrome locally stored data.

            The problem is, that if User One logs out, but does not close the browser, and then User Two logs in, the API does not get refreshed / re-logged. So, when User Two goes to the the API, it appears to be as if it's really User One.

            So, I was attempting to front-run the API's cookies by setting identical ones first, but with a very short expiration time to force the re-login to the API. The code we've been discussing here does indeed set a cookie for A5 -- I can see it when I run A5W_Info() for instance. But the code we're discussing here does not store cookies in the same place as the API -- in Chrome's Locally Stored Data.

            So, what I'd like to do is remove the API cookies or modify them at User Login time. That doesn't seem possible, so I was hoping to establish them first -- before the API does -- with a short expiration, not the "When the Browser Closes" expiration.

            Make sense? Any ideas?
            -Steve
            sigpic

            Comment


              #7
              Re: Cookie syntax

              If the API's server set's a cookie, you cannot overwrite or replace that cookie from a different server (your Alpha App Server). Only the original server, or client-side code working with a response from that server, can modify the cookie. Is there an API call to log out a user or otherwise invalidate the cookies? If so, do this as part of your OERCA login.

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

              Comment


                #8
                Re: Cookie syntax

                Thanks Lenny. Turns out all I need to do is make sure my browser goes to their logout page. And, their setup redirects their logout page to a page of my choice. So, with a couple of response.redirect()s I got 'er done.

                Press release on this integration probably coming soon.
                -Steve
                sigpic

                Comment

                Working...
                X