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

Dialog to a5w page 403 error

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

    Dialog to a5w page 403 error

    Using an old-fashioned dialog to redirect a page - even where security is set to "always allowed" I get the following error:
    403 Forbidden

    Your security credentials do not allow access to this resource.
    The code is simply
    Code:
    currentform.RedirectTarget = "variables.a5w"
    Is this a bug?

    P.S. Yes, I published page security.
    Peter
    AlphaBase Solutions, LLC

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



    #2
    Re: Dialog to a5w page 403 error

    Peter, I get that error if the page is not found (a misspelled page name for example) as well as if the security settings are not right.
    Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

    Comment


      #3
      Re: Dialog to a5w page 403 error

      Originally posted by frankbicknell View Post
      Peter, I get that error if the page is not found (a misspelled page name for example) as well as if the security settings are not right.
      Unfortunately, security settings are right and the spelling is correct.
      Peter
      AlphaBase Solutions, LLC

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


      Comment


        #4
        Re: Dialog to a5w page 403 error

        Test with a known-good page like currentform.RedirectTarget = "index.a5w"
        Steve Wood
        See my profile on IADN

        Comment


          #5
          Re: Dialog to a5w page 403 error

          The redirect should be insignificant. Can you properly access the page by directly entering the URL in the browser's address bar?

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

          Comment


            #6
            Re: Dialog to a5w page 403 error

            Originally posted by Lenny Forziati View Post
            The redirect should be insignificant. Can you properly access the page by directly entering the URL in the browser's address bar?
            Lenny, yes the page does display when I do it directly like that.

            However, I'm working within a tabbed_ui if that matters. I tested in localhost running the page w. the dialog directly and the redirect still returns the same security error. Security is published.
            Peter
            AlphaBase Solutions, LLC

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


            Comment


              #7
              Re: Dialog to a5w page 403 error

              Originally posted by Peter.Greulich View Post
              Lenny, yes the page does display when I do it directly like that.

              However, I'm working within a tabbed_ui if that matters. I tested in localhost running the page w. the dialog directly and the redirect still returns the same security error. Security is published.
              Enable the raw HTTP log and look to see what is different between the request created by the redirect and your direct entry of the URL.

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

              Comment


                #8
                Re: Dialog to a5w page 403 error

                Here are the results:

                ****************************************
                18/May/2011:13:26:58 -0400
                127.0.0.1
                GET /Montech/variables.a5wtempreport.txt?132658000 HTTP/1.1
                Host: localhost
                User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
                Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
                Accept-Language: en-us,en;q=0.5
                Accept-Encoding: gzip, deflate
                Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
                Keep-Alive: 115
                Connection: keep-alive
                Referer: http://localhost/Montech/UnitReturns.a5w - this is the calling page
                Cookie: A5wBrowserId=0c5d21865f384dceb765e900ea09d7ae; A5wSessionId=788b2d7307ed40e5b164aa5b03094557; a5ws_7c0fa05f9ffe4ebe80ca199a94e3e9e9=


                ****************************************
                ****************************************
                18/May/2011:13:26:58 -0400

                R>>> HTTP/1.1 403 Forbidden
                R>>> Server: Alpha Five/10.0 Build/4091-3658
                R>>> Date: Wed, 18 May 2011 17:26:58 GMT
                R>>> Content-Type: text/html
                R>>> Content-Length: 217
                R>>> Accept-Ranges: none
                R>>> Connection: Keep-Alive
                R>>> Set-Cookie: A5wSessionId=788b2d7307ed40e5b164aa5b03094557; HttpOnly; path=/
                R>>> Set-Cookie: A5wBrowserId=0c5d21865f384dceb765e900ea09d7ae; expires=Fri, 17-Jun-2011 17:26:58 GMT; HttpOnly; path=/
                R>>>
                R>>> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
                R>>> <html><head>
                R>>> <title>403 Forbidden</title>
                R>>> </head><body>
                R>>> <h1>403 Forbidden</h1>
                R>>> Your security credentials do not allow access to this resource.<p>
                R>>> </body></html>
                ****************************************
                18/May/2011:13:28:51 -0400
                127.0.0.1
                GET /Montech/variables.a5w HTTP/1.1
                Host: localhost
                User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
                Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
                Accept-Language: en-us,en;q=0.5
                Accept-Encoding: gzip, deflate
                Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
                Keep-Alive: 115
                Connection: keep-alive
                Cookie: A5wBrowserId=0c5d21865f384dceb765e900ea09d7ae; A5wSessionId=788b2d7307ed40e5b164aa5b03094557; a5ws_7c0fa05f9ffe4ebe80ca199a94e3e9e9=


                ****************************************
                ****************************************
                18/May/2011:13:28:51 -0400

                R>>> HTTP/1.1 500 Internal Server Error
                R>>> Server: Alpha Five/10.0 Build/4091-3658
                R>>> Date: Wed, 18 May 2011 17:28:51 GMT
                R>>> Content-Type: text/html
                R>>> Content-Length: 344
                R>>> Accept-Ranges: none
                R>>> Connection: Keep-Alive
                R>>> Set-Cookie: A5wSessionId=788b2d7307ed40e5b164aa5b03094557; HttpOnly; path=/
                R>>> Set-Cookie: A5wBrowserId=0c5d21865f384dceb765e900ea09d7ae; expires=Fri, 17-Jun-2011 17:28:51 GMT; HttpOnly; path=/
                R>>>
                R>>> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
                R>>> <html><head>
                R>>> <title>500 Internal Server Error</title>
                R>>> </head><body>
                R>>> <h1>500 Internal Server Error</h1>
                R>>> "<b>Script Error</b><br />Error:Script: /Montech/variables.a5w line:23<br />?session.cust_filter<br />Property not found
                R>>> <br />session.cust_filter subelement not found."
                R>>> </body></html>
                The errors in the variables page is only because the vars don't exist.
                Peter
                AlphaBase Solutions, LLC

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


                Comment


                  #9
                  Re: Dialog to a5w page 403 error

                  Take a closer look at the requests Peter, specifically what I have made bold. Something in your code for the redirect is constructing the wrong page name.

                  Originally posted by Peter.Greulich View Post
                  Here are the results:

                  Code:
                  ****************************************
                  18/May/2011:13:26:58 -0400
                  127.0.0.1
                  GET [SIZE="5"][B][B]/Montech/variables.a5wtempreport.txt?132658000[/B][/B][/SIZE] HTTP/1.1
                  Host: localhost
                  User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
                  Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
                  Accept-Language: en-us,en;q=0.5
                  Accept-Encoding: gzip, deflate
                  Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
                  Keep-Alive: 115
                  Connection: keep-alive
                  Referer: http://localhost/Montech/UnitReturns.a5w - this is the calling page
                  Cookie: A5wBrowserId=0c5d21865f384dceb765e900ea09d7ae; A5wSessionId=788b2d7307ed40e5b164aa5b03094557; a5ws_7c0fa05f9ffe4ebe80ca199a94e3e9e9=
                  
                  
                  ****************************************
                  ****************************************
                  18/May/2011:13:26:58 -0400
                  
                  R>>> HTTP/1.1 403 Forbidden
                  R>>> Server: Alpha Five/10.0 Build/4091-3658
                  R>>> Date: Wed, 18 May 2011 17:26:58 GMT
                  R>>> Content-Type: text/html
                  R>>> Content-Length: 217
                  R>>> Accept-Ranges: none
                  R>>> Connection: Keep-Alive
                  R>>> Set-Cookie: A5wSessionId=788b2d7307ed40e5b164aa5b03094557; HttpOnly; path=/
                  R>>> Set-Cookie: A5wBrowserId=0c5d21865f384dceb765e900ea09d7ae; expires=Fri, 17-Jun-2011 17:26:58 GMT; HttpOnly; path=/
                  R>>>
                  R>>> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
                  R>>> <html><head>
                  R>>> <title>403 Forbidden</title>
                  R>>> </head><body>
                  R>>> <h1>403 Forbidden</h1>
                  R>>> Your security credentials do not allow access to this resource.<p>
                  R>>> </body></html>
                  ****************************************
                  18/May/2011:13:28:51 -0400
                  127.0.0.1
                  GET [SIZE="5"][B][B]/Montech/variables.a5w[/B][/B][/SIZE] HTTP/1.1
                  Host: localhost
                  User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
                  Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
                  Accept-Language: en-us,en;q=0.5
                  Accept-Encoding: gzip, deflate
                  Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
                  Keep-Alive: 115
                  Connection: keep-alive
                  Cookie: A5wBrowserId=0c5d21865f384dceb765e900ea09d7ae; A5wSessionId=788b2d7307ed40e5b164aa5b03094557; a5ws_7c0fa05f9ffe4ebe80ca199a94e3e9e9=
                  
                  
                  ****************************************
                  ****************************************
                  18/May/2011:13:28:51 -0400
                  
                  R>>> HTTP/1.1 500 Internal Server Error
                  R>>> Server: Alpha Five/10.0 Build/4091-3658
                  R>>> Date: Wed, 18 May 2011 17:28:51 GMT
                  R>>> Content-Type: text/html
                  R>>> Content-Length: 344
                  R>>> Accept-Ranges: none
                  R>>> Connection: Keep-Alive
                  R>>> Set-Cookie: A5wSessionId=788b2d7307ed40e5b164aa5b03094557; HttpOnly; path=/
                  R>>> Set-Cookie: A5wBrowserId=0c5d21865f384dceb765e900ea09d7ae; expires=Fri, 17-Jun-2011 17:28:51 GMT; HttpOnly; path=/
                  R>>>
                  R>>> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
                  R>>> <html><head>
                  R>>> <title>500 Internal Server Error</title>
                  R>>> </head><body>
                  R>>> <h1>500 Internal Server Error</h1>
                  R>>> "<b>Script Error</b><br />Error:Script: /Montech/variables.a5w line:23<br />?session.cust_filter<br />Property not found
                  R>>> <br />session.cust_filter subelement not found."
                  R>>> </body></html>
                  The errors in the variables page is only because the vars don't exist.

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

                  Comment


                    #10
                    Re: Dialog to a5w page 403 error

                    I think you're right, Lenny. More later...
                    Peter
                    AlphaBase Solutions, LLC

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


                    Comment


                      #11
                      403 error in TabbedUI -&gt; report

                      .
                      Hi,
                      I have a similar issue to what is happening to Peter Greulich. This is what I have done:
                      • Build a report
                      • Create a new TabbedUI component and include the report
                      • A TabbedUI page was created by Alpha Five, which I renamed
                      • In Web Security
                        • In Page Security, select the TabbedUI page and set it to "Always Allowed"
                        • In Component Security, select the TabbedUI component and set it to "Always Allowed"
                        • In Component Security, select the report and set it to "Always Allowed"
                        • Publish Security Files
                      • Publish
                        • the TabbedUI page
                        • the TabbedUI component
                        • the database tables


                      With the Application Server running, go to the browser, login and go to the TabbedUI page. The page shows, but when clicking on the button (corresponding to the report) I get this message:

                      XHTTPRequest Error:

                      403 Forbidden
                      Your security credentials do not allow access to this resource

                      Alpha Five/11.0 Build/2549-3903 at AJFMAIN Port 80


                      If I turn Web Security off, the report shows. Otherwise, I get the above error. I have no clue on how to fix this. Any tips would be very appreciated.




                      Regards,
                      Felix
                      .

                      Comment

                      Working...
                      X