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

Outbound Proxy issue

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

    Outbound Proxy issue

    We are trying to use http_get from a web application but are getting this error:

    Could not connect to server: WSAECONNREFUSED - Connection refused while connecting.

    Detailed Description:
    No connection could be made because the target computer actively refused it.
    This usually results from trying to connect to a service that is inactive on the
    foreign host�that is, one with no server application running.

    It is caused by our proxy server not receiving proper authentication information.

    How can we send an outbound request via the WAS that will authenticate with our proxy?

    We thought about using HTTP_GET_PAGE2() but see this warning in the documentation: HTTP_GET_PAGE2() is not server-safe and cannot be used in an A5W environment.

    Thanks,

    -Doug
    Tags: None
    #2
    Re: Outbound Proxy issue

    Do you mean http Basic Authentication?

    Comment

      #3
      Re: Outbound Proxy issue

      Ken,

      Thanks for the quick reply.

      Originally posted by kkfin View Post
      Do you mean http Basic Authentication?
      No, we are referring to authentication for our firewall proxy. It won't let us make outgoing HTTP requests without credentials.

      Thanks,

      -Doug

      Comment

        #4
        Re: Outbound Proxy issue

        I googled. Check this php example, but it may give you some ideas...
        http://stackoverflow.com/questions/1...behind-a-proxy

        Comment

          #5
          Re: Outbound Proxy issue

          Andy,

          Thanks for the suggestions. Unfortunately we were unable to get that to work. Here's what we tried as a test:

          dim p as P
          dim fp as P
          dim blob as B
          dim length as n

          fp = file.open("C:\TEMP\test_bas64encode.txt", FILE_RO_SHARED) 'File with credentials in usr:pass format
          length = fp.bytes_get()
          blob = fp.readb(length)

          fp.close()

          auth = base64encode(blob)

          dim p.host as C = "www.alphasoftware.com"

          dim p.page as C = "/"
          dim p.header as c = "Proxy-Authorization: Basic " + auth

          dim alpha as P

          alpha = http_fetch(p)

          a5_show_html(alpha.body)

          Is there a different function we could be using, perhaps?

          Thanks,

          -Doug

          Comment

            #6
            Re: Outbound Proxy issue

            For additional information, we are using an M86 Secure Web Gateway for the proxy. Anyone have experience with this?

            thanks,

            -Doug

            Comment

              #7
              Re: Outbound Proxy issue

              You could manually hardcode the auth = base64encode(user:password) to be sure there is no file issue.
              But the more fundamental issue relates to not being able to indicate the IP:port of the proxy!!
              You may need to send an e-mail to Alpha (or send a bug report) asking for their help - I have never attempted this in Alpha, so I am of no use really.

              Comment

                #8
                Re: Outbound Proxy issue

                Andy,

                Originally posted by agillbb View Post
                You could manually hardcode the auth = base64encode(user:password) to be sure there is no file issue.
                But the more fundamental issue relates to not being able to indicate the IP:port of the proxy!!
                You may need to send an e-mail to Alpha (or send a bug report) asking for their help - I have never attempted this in Alpha, so I am of no use really.
                We tried the base64encode function manually first, but it failed because it requires a blob type rather than character. Looking at the documentation for base64encode, we copied what was there.

                RE: IP:port of proxy, that is exactly the issue we face, and we have sent an email to Alpha on this issue. Still awaiting a reply.

                One thing we are considering is using cURL and some how firing it from Alpha. Still trying to figure if that will work at all.

                Thanks,

                -Doug

                Comment

                  #9
                  Re: Outbound Proxy issue

                  Originally posted by djvdm View Post
                  RE: IP:port of proxy, that is exactly the issue we face, and we have sent an email to Alpha on this issue. Still awaiting a reply.
                  I am not sure if the problem is that you don't know the port number or what but you just add the port number
                  to pointer variable like this:

                  dim p.port as N = 1234

                  But this is maybe not your problem because this syntax reads clear in help file.

                  Comment

                  Previous template Next
                  Working...
                  X