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

Problem passing parameters to http_fetch

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

  • Problem passing parameters to http_fetch

    Hi
    I try to run a GET to some api, using http_fetch, and no matter how i tried to urlencode the parameters, they are always disregarded.

    I have the following parameters:
    Code:
    $filter=POR_BOOKNUM eq '2108110096'&$select=IVNUM, DISPRICE
    with the spaces in it and the $ signs etc...
    When sending from AA with http_fetch the parameters are discarded.
    In chrome, calling
    Code:
    https://myurl/myfunction?$filter=POR_BOOKNUM eq '2108110096'&$select=IVNUM, DISPRICE
    works perfectly and the parameters are recognized.
    Also with postman, works successfully.

    Do you have any idea what could be wrong in the way i setup my http_fetch call? tried urlencoding the whole parameters string, as well as urlencode("$filter=POR_BOOKNUM eq '2108110096'")+"&"+urlencode("$select=IVNUM, DISPRICE") but still doesn't work...

    Thanks
    Jaime

  • #2
    Hi Jaime,

    Is this an API you created, or one you are hoping to consume ?

    If the URL works great, it's sometimes easier to use strtran() and stuff() to change the various parts of the URL rather than
    mess with the setting for fetch.
    Gregg
    https://paiza.io is a great site to test and share sql code

    Comment


    • #3
      If you look in the Chrome Developer Tools, you can see how the URL is encoded before being sent to the server when you access the URL with it "unencoded":

      encoded.png

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

      Comment


      • #4
        Originally posted by madtowng View Post
        Hi Jaime,

        Is this an API you created, or one you are hoping to consume ?

        If the URL works great, it's sometimes easier to use strtran() and stuff() to change the various parts of the URL rather than
        mess with the setting for fetch.
        It's something i'm consuming

        Comment


        • #5
          Originally posted by Lenny Forziati View Post
          If you look in the Chrome Developer Tools, you can see how the URL is encoded before being sent to the server when you access the URL with it "unencoded":

          encoded.png
          Thanks Lenny, i think i already tried entering the unencoded string manually, but failed, i may have entered a typo while doint it. Will give it another try...

          Comment


          • #6
            Two things.
            1. It's always helpful to share the api documentation.
            2. You might want to use the url_encode() function if you're not already using it.
            Gregg
            https://paiza.io is a great site to test and share sql code

            Comment


            • #7
              Originally posted by Lenny Forziati View Post
              If you look in the Chrome Developer Tools, you can see how the URL is encoded before being sent to the server when you access the URL with it "unencoded":

              encoded.png
              As i wrote before, i hardcoded the settings.body parameter exactly as shown here, and it still is not recognized correctly, it's as if i didn't set any parameter at all...Will try with curl to check if that will work, but i'm puzzled as to why i can't use http_fetch
              Edit: i set the "show before send" flag in the http_fetch call, and i don't see the settings.body at all, just the host name and the headers...i forgot to mention i am trying to run a GET. So i changed to POST and now i see the parameter in the preview, but get some error about content type not set...will keep on digging
              Last edited by WindForce; 11-15-2021, 12:51 AM.

              Comment


              • #8
                Using Curl this works correctly...weird

                Comment


                • #9
                  if you test with very simple parameters eg ?p1=123 do the parameters get passed correctly via HTTP get using the query string. Obviously, the API will return an error.
                  https://appsbydesign.co.uk/

                  Comment


                  • #10
                    As i wrote before, i hardcoded the settings.body parameter exactly as shown here, and it still is not recognized correctly, it's as if i didn't set any parameter at all...Will try with curl to check if that will work, but i'm puzzled as to why i can't use http_fetch
                    Edit: i set the "show before send" flag in the http_fetch call, and i don't see the settings.body at all, just the host name and the headers...i forgot to mention i am trying to run a GET. So i changed to POST and now i see the parameter in the preview, but get some error about content type not set...will keep on digging
                    An HTTP get does not use a body, so if you are doing a GET and specifying a POST body, that body will be omitted. This is the correct behavior. You should be sending your parameters as a query string for a GET.

                    Simply switching to a POST won't work either. While the body will now be sent, you would need to specify the content type of the body, and it sounds this is exactly what the API complained that you did not do. If you are sending what should be a query string as a POST body instead, and it is URL encoded name-value pairs, the correct content type is application/x-www-form-urlencoded

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

                    Comment


                    • #11
                      Thanks Lenny, i realized that after posting my findings here with GET and POST. Putting the whole url in GET still failed for some reason, and i didn't know what content-type to use for POST. Now that you wrote it here, i tested a POST and it finally works as expected...phewww...

                      Comment

                      Working...
                      X