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

403 error, ONLY in IE, NOT in FireFox and Chrome, Build 4091-3658 Mar-8-2011

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

    403 error, ONLY in IE, NOT in FireFox and Chrome, Build 4091-3658 Mar-8-2011

    In exact the same setting I get ONLY in IE an acces arror (403), Chrome / Firefox no problem at all. It is some xbasic code, called from the nav component to switch language and redirect to correct page. It is placed in 2 pages:

    page 1:
    session.__protected__previous_language = session.__protected__activeLanguage
    session.__protected__Previous_page = Request.Referer

    response.redirect("4vastgoed_language_english.a5w")


    page 2 (= page to which page 1 redirects)

    Has a nav component on it (just in case the redirect on page 2 fails) and as xbasic codeblock:

    DIM referer as C
    DIM extpos as N


    'In the intermediate page 4vastgoed_language_set_english
    'session.__protected__previous_language = session.__protected__activeLanguage
    'session.__protected__Previous_page = Request.Referer
    'have been stored

    'set new language and send user to last visited page in new language

    session.__protected__activeLanguage="english"


    if 1=1
    select
    case session.__protected__previous_language="default"

    referer = Request.Referer
    extpos = atc(".a5w",referer)-1
    referer = substr(referer,1,extpos)+"_"+session.__protected__activeLanguage+".a5w"
    session.__protected__Redirect_page = referer

    response.redirect(session.__protected__Redirect_page)



    case session.__protected__previous_language="german"

    referer = Request.Referer
    extpos = atc("_german.a5w",referer)-1
    referer = substr(referer,1,extpos)+"_"+session.__protected__activeLanguage+".a5w"
    session.__protected__Redirect_page = referer

    response.redirect(session.__protected__Redirect_page)

    end select

    else
    'include footer
    a5w_include("Footer_copyright.a5w")
    'include and hide documentation page
    if session.showdocpage="on"
    a5w_include("Doc_index.a5w")
    else
    End if
    end if


    Page 2 does not open, in page 1 the IE 403 error already occurs.

    Any idea why this would fail in IE and NOT in FF / Chrome?

    Thanks in advance

    Ger
    Ger Kurvers
    Alpha Anywhere / V4.6.1.9- Build 6488 (production) / V4.6.5.1 - 8722-5683(testing)
    Development: Mysql, windows 10 64 Applicationserver: standard on Windows server 2019

    #2
    Re: 403 error, ONLY in IE, NOT in FireFox and Chrome, Build 4091-3658 Mar-8-2011

    What version of IE?

    Comment


      #3
      Re: 403 error, ONLY in IE, NOT in FireFox and Chrome, Build 4091-3658 Mar-8-2011

      Originally posted by MichaelCarroll View Post
      What version of IE?
      IE version 7.0.6002.18005 But i have also seen it at version 8.

      If you want to test it yourself :-)

      goto demo.4vastgoed.nl
      user: [email protected]
      password: geheim
      Switch after loging to english

      Just don't try it at "quicksearch" menu option: i know that has an issue also, but it is caused by something else.
      Ger Kurvers
      Alpha Anywhere / V4.6.1.9- Build 6488 (production) / V4.6.5.1 - 8722-5683(testing)
      Development: Mysql, windows 10 64 Applicationserver: standard on Windows server 2019

      Comment


        #4
        Re: 403 error, ONLY in IE, NOT in FireFox and Chrome, Build 4091-3658 Mar-8-2011

        I see the error with version ie8.

        Does this happen while publishing to local host?

        Comment


          #5
          Re: 403 error, ONLY in IE, NOT in FireFox and Chrome, Build 4091-3658 Mar-8-2011

          Originally posted by MichaelCarroll View Post
          I see the error with version ie8.

          Does this happen while publishing to local host?
          On local host i have the same issue, but i waited with posting this issue until i could test it also on a non local host testserver.... (the one you tested)
          Ger Kurvers
          Alpha Anywhere / V4.6.1.9- Build 6488 (production) / V4.6.5.1 - 8722-5683(testing)
          Development: Mysql, windows 10 64 Applicationserver: standard on Windows server 2019

          Comment


            #6
            Re: 403 error, ONLY in IE, NOT in FireFox and Chrome, Build 4091-3658 Mar-8-2011

            Additional information: further testing showed that this issue was also present with build 3597-3620. It just escaped testing until now :-(.
            But the main question stays: why only in IE and not in FF/Chrome an issue?
            Ger Kurvers
            Alpha Anywhere / V4.6.1.9- Build 6488 (production) / V4.6.5.1 - 8722-5683(testing)
            Development: Mysql, windows 10 64 Applicationserver: standard on Windows server 2019

            Comment


              #7
              Re: 403 error, ONLY in IE, NOT in FireFox and Chrome, Build 4091-3658 Mar-8-2011

              English goes to different pages depending on browser:

              IE: ...4vastgoed/_english.a5w
              Chrome: ...4vastgoed/4vastgoed_myinfo_english.a5w

              Notice the space just before the page name for IE.
              Steve Wood
              See my profile on IADN

              Comment


                #8
                Re: 403 error, ONLY in IE, NOT in FireFox and Chrome, Build 4091-3658 Mar-8-2011

                Originally posted by Steve Wood View Post
                English goes to different pages depending on browser:

                IE: ...4vastgoed/_english.a5w
                Chrome: ...4vastgoed/4vastgoed_myinfo_english.a5w

                Notice the space just before the page name for IE.
                Thanks Steve (where could you see that?)

                But: i have no browser depending code :-(

                Why would

                -----start code ----

                select
                case session.__protected__previous_language="default"

                referer = Request.Referer
                extpos = atc(".a5w",referer)-1
                referer = substr(referer,1,extpos)+"_"+session.__protected__activeLanguage+".a5w"
                session.__protected__Redirect_page = referer

                response.redirect(session.__protected__Redirect_page)
                ------- end code ------

                behave different in IE versus Chrome/FF?
                Ger Kurvers
                Alpha Anywhere / V4.6.1.9- Build 6488 (production) / V4.6.5.1 - 8722-5683(testing)
                Development: Mysql, windows 10 64 Applicationserver: standard on Windows server 2019

                Comment


                  #9
                  Re: 403 error, ONLY in IE, NOT in FireFox and Chrome, Build 4091-3658 Mar-8-2011

                  I didn't look at your code, I saw it in the browser address bar. It's the same situation if you select Dutch.

                  If you are trying to parse the page name using that atc function, it is easier to use the a5_split_url function.
                  Steve Wood
                  See my profile on IADN

                  Comment


                    #10
                    Re: 403 error, ONLY in IE, NOT in FireFox and Chrome, Build 4091-3658 Mar-8-2011

                    Originally posted by Steve Wood View Post
                    I didn't look at your code, I saw it in the browser address bar. It's the same situation if you select Dutch.

                    If you are trying to parse the page name using that atc function, it is easier to use the a5_split_url function.
                    Thanks Steve for pointing me to the a5_split_url function. Indeed easier.

                    I pinpointed the problem, but cannot think of a solution:

                    Make a simple A5 page with 1 line of code:

                    ?request.referer

                    In IE it throws blank, in Chrome, FF it works like documented and gives the refering page as result :-)

                    So the problem is already in page 1 of my example

                    Is this a bug? / Work around?
                    Ger Kurvers
                    Alpha Anywhere / V4.6.1.9- Build 6488 (production) / V4.6.5.1 - 8722-5683(testing)
                    Development: Mysql, windows 10 64 Applicationserver: standard on Windows server 2019

                    Comment


                      #11
                      Re: 403 error, ONLY in IE, NOT in FireFox and Chrome, Build 4091-3658 Mar-8-2011

                      Have to assume the browsers are all working as they should, request.referer has a long history. Also, I use this function quite a bit to 'bring users back to the calling page' and so a lot would be broken if the function did not work.

                      Your code does a lot of moving values from var to var. So you need to isolate at which point the result goes south. Who knows, 'referer' might be a reserved IE word, if there is such a thing.

                      Another way to approach your language separation is to prefix all English pages with _en_ and all Dutch pages with _nl_ or similar. Then when they select a language just set a single session var that you would then use to select the appropriate Navigation Component. You'd have a nav component for each language. The nav would be in the proper language, and it would be set to call the appropriate pages. You can "stack" nav components and select the one you want like this:

                      select
                      case session.__protected__lang = "en"
                      ?x_nav_main_en.Output.Body.navsysTBH
                      case session.__protected__lang = "fr"
                      ?x_nav_main_fr.Output.Body.navsysTBH
                      case else
                      ?x_nav_main_nl.Output.Body.navsysTBH
                      end select

                      ---------
                      Computer history buffs -- ever notice that "referer" is spelled wrong?
                      Steve Wood
                      See my profile on IADN

                      Comment


                        #12
                        Re: 403 error, ONLY in IE, NOT in FireFox and Chrome, Build 4091-3658 Mar-8-2011

                        Request.Referer simply contains the value of the Referer header sent by the client.
                        • Many, though not all, browsers will include a referer header to indicate the last page that was visited.
                        • It is extremely common for browsers that do include a referer header to allow the sending of it to be turned off.
                        • Many firewalls and privacy software suites strip or sanitize any referer information.


                        As such, Request.Referer is extremely unreliable for any type of decision making such as this. It can give you some insight as to the source of some of the visits to your sight, but you should never try to use it in the way you are, because when the header doesn't have an expected value, your code fails.

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

                        Comment


                          #13
                          Re: 403 error, ONLY in IE, NOT in FireFox and Chrome, Build 4091-3658 Mar-8-2011

                          Originally posted by Steve Wood View Post
                          ---------
                          Computer history buffs -- ever notice that "referer" is spelled wrong?
                          Not that it matters, but from Wikipedeia:

                          Origin of the term referer

                          The misspelling referer originated in the original proposal by computer scientist Phillip Hallam-Baker to incorporate the field into the HTTP specification.[1] The misspelling was set in stone by the time of its incorporation into the standards document Request for Comments (RFC) 1945; document co-author Roy Fielding has remarked that neither "referrer" nor the misspelling "referer" were recognized by the standard Unix spell checker of the period.[2] "Referer" has since become a widely used spelling in the industry when discussing HTTP referrers; usage of the misspelling is not universal, though, as the correct spelling of "referrer" is used in some web specifications such as the Document Object Model.
                          Peter
                          AlphaBase Solutions, LLC

                          [email protected]
                          https://www.alphabasesolutions.com


                          Comment


                            #14
                            Re: 403 error, ONLY in IE, NOT in FireFox and Chrome, Build 4091-3658 Mar-8-2011

                            Thanks Lenny for the explanation and advice. I will implement another method for language switching in combination with the nav component.

                            Maybe a little warning regarding request.referer in the wiki wil save future new a5 users a lot of work.
                            Ger Kurvers
                            Alpha Anywhere / V4.6.1.9- Build 6488 (production) / V4.6.5.1 - 8722-5683(testing)
                            Development: Mysql, windows 10 64 Applicationserver: standard on Windows server 2019

                            Comment


                              #15
                              Re: 403 error, ONLY in IE, NOT in FireFox and Chrome, Build 4091-3658 Mar-8-2011

                              Thanks Lenny, guess I need to revisit my usage of request.referer.
                              Steve Wood
                              See my profile on IADN

                              Comment

                              Working...
                              X