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

Web Application - identify Client's machine

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

    Web Application - identify Client's machine

    Either from a Web Page or a Component, I need to be able to identify the IP Address or the Machine Name (or anything similar) of the Client doing the browsing - either will do. Using API_GETMACHINENAME() doesn't do it - instead it gives the name of our Web Server (on which Alpha5 WAS is running); I've also tried several of the Request."variables", but no joy there either.
    Tags: None
    #2
    RE: Web Application - identify Client

    Check out a5w_info(), it will show you all of the information that is available to you as Request and Server variables. (sample output)


    Request.REMOTE_ADDR is the IP address of the remote machine.


    Additionally, session.session_id will be unique to each remote machine.

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

    Comment

      #3
      RE: Web Application - identify Client

      I've tried the following tests:

      "p"COMPUTERNAME :
      "%a5
      ? api_getenvironmentvar("COMPUTERNAME")
      %"

      USERPROFILE :

      "%a5
      ? api_getenvironmentvar("USERPROFILE")
      %"

      "/p"

      ...but the results refer again to the Web Server, not the remote Client.

      Comment

        #4
        RE: Web Application - identify Client

        Correct, all Xbasic is executed on the server so you will get the server's information. Have you looked at Request.REMOTE_ADDR as I suggested? This is all you'll be able to get without asking the user to give you more.

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

        Comment

          #5
          RE: Web Application - identify Client

          Yes - have done Request.REMOTE_ADDR too - that gives the addr. of the ISA Server. Route of traffic goes like this:

          My Client/Browser session -"
          ISP -"
          Our ISA Server -"
          Our Web Server.

          Perhaps a no-go area at the moment, then?

          Comment

            #6
            RE: Web Application - identify Client

            If there's a proxy or a NAT firewall, that's the IP address you'll get. For example, AOL's millions of users typically show up as one of 5 or so IP addresses.

            Do you really need an IP address/name, or just a unique identifier from each client? I mentioned session.session_id, but did not really give much info on it.

            session_is is actually a bit of a misnomer int he current implementaion, it is actually a unique client ID. Each unique web browser will get a unique session.session_id and that value will always be the same, even across sessions.

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

            Comment

              #7
              RE: Web Application - identify Client

              OK. Yes, an IP or MachineName of the Client itself, rather than that of the Firewall or Web Server, was what I was after.

              However, I've done some tests using the .SessionID option and, although it is fairly meaningless, it is at least consistent as being unique to a given Browser so that will have to do for our purposes for the time being.

              Last question on this one so I can implement a solution: what is the maximum length a SessionID could be (ie how many characters)?

              Thanks for your advice and prompt responses - much appreciated.

              Comment

                #8
                RE: Web Application - identify Client

                The session id is always 32 characters.

                The session id is no less meaningless than IP address if you are not the administrator of the user network. If you are the administrator, you can determine which machine uses which session, just as you can determine which machine has which IP address.

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

                Comment

                Previous template Next
                Working...
                X