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

XHTTPRequest Error / 403 Forbidden

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

  • XHTTPRequest Error / 403 Forbidden

    I having a heck of a time since the most recent update, and I'm wondering if anyone else is experiencing the same issue before I submit a bug report -

    After the latest update (2787_3538 - 03-04-10) a bunch of my users are getting this message when they perform any action on the screen that initiates an Ajax callback:

    XHTTPRequest Error
    403 Forbidden
    Your security credentials do now allow access to this resource.

    The weird thing is that it doesn't happen on all computers. The same user can log into two different computers, and will have no problem on one, but get the above message on the other. (All are IE 7.0 or above however.)

    I've since tried rolling back to some previous patches, but this has not fixed the problem, even though it did not occur until the most recent patch was applied.

    ** Update at 2100 Hrs. - After some investigation, it appears that the problem is limited to pages that were originally built in V9, and have the "Ajax Enabled" box checked. Unchecking this box removes the errors because the ajax callbacks are no longer working, but the user loses the advanced features of Ajax, and the page runs much slower. This may be related to the recent announcement by Alpha: "Removal of the V9 Compatability Server."
    Last edited by Rich Hartnett; 03-08-2010, 10:02 PM.
    Sergeant Richard Hartnett
    Hyattsville City Police Department
    Maryland

  • #2
    Re: XHTTPRequest Error / 403 Forbidden

    I think that happens when component level security is activated and you dont have permissions to open the grid or the session expires
    Cheers
    Mauricio

    Comment


    • #3
      Re: XHTTPRequest Error / 403 Forbidden

      Thanks Mauricio.

      That may not be the problem for me though, because I do not have component level security activated on any of my components. Everything is done by page security.

      As for session timeouts, the problem happens even if the user has just logged in and navigates directly to the "problem page."

      I'm going to submit a bug report. I really don't want to have to rebuild all of these problem pages.
      Sergeant Richard Hartnett
      Hyattsville City Police Department
      Maryland

      Comment


      • #4
        Re: XHTTPRequest Error / 403 Forbidden

        Rich I have noticed that if I put some of my older grids on Tabbed UI's I get an error saying that this grid is not ajax grid but if I edit the grid it seems that ajax is turned on. I turn off the ajax modify something else save and publish the grid,go back and turn ajax back on save and publish it wont give me the error again.
        Maybe not a solution but a clue.
        Chad Brown

        Comment


        • #5
          Re: XHTTPRequest Error / 403 Forbidden

          i experience something strange with this "XHTTP Request Error",

          in my client for some of computers it does work well without XHTTP Request Error (vista or XP),
          but for some computer (XP operating system) i found that using IE8 and FireFox it will produce "XHTTP Request Error", but when i install google chrome then it work ok (problem solved),

          but for some computer (XP operating system) although i tried using all browser (IE8, Firefox and Google chrome) and still it doesn't work, i got "XHTTP Request Error" when i click add new button or save button.

          do any body experience the samething? any advise?

          Thanks,
          Andy

          Comment


          • #6
            Re: XHTTPRequest Error / 403 Forbidden

            I think the problem is solved, and very quickly I might add! I submitted a bug report just a little while ago, and Martin Heller responded almost immediately with the following solution:

            Richard, please turn Ajax back on in your grids and try Edit|Bulk Operation|Update Compiled Files for Ajax Grids, followed by a full republish after clearing the publication history.

            I almost forgot: there's an item on the Bulk Operation menu to turn Ajax on or off that you can use before the bulk compile. The bulk operations take the sting out of cleaning things up.
            Although I had performed "step one" before he sent the second email regarding the turning off of Ajax, it seems to have solved the problem.

            I haven't had the chance to check all of the grids that I had originally created in V9, but of the ones I've checked, so far, so good.

            Ya gotta love the A5 customer service.
            Sergeant Richard Hartnett
            Hyattsville City Police Department
            Maryland

            Comment


            • #7
              Re: XHTTPRequest Error / 403 Forbidden

              I am running the latest version V10 and receiving this error on different machines with different browsers. I have tried bulk turning off ajax and compiling all, clearing history republishing ( blows up ) . Bulk turn it back on , compile, clear history, published and still the error shows up on other machines. My system works fine on these IE7, FIrefox 3.6.3 and Chrome, but the presidents office, however IE8 doesn't work and Chrome doesn't work when you try to use the AJAX operations -- throws the error.

              I am migrating this application from Ver9 to 10 and have been testing using IE7 exclusively on my machine. We were going to turn on 10 today so I brought all the ver 9 DBFs over to the development system and republished them to the server. I have rebuilt all grid.a5w's in v10 to get rid of the WARNING about page security. Anyone know how I can save face?

              BTW, I know its my fault. It has to be. No one else has complained.

              Comment


              • #8
                Re: XHTTPRequest Error / 403 Forbidden

                There are only a few limited reasons to get a 403 error. Please reference this thread, this thread, this Wiki entry, or this Wiki entry.

                If the problem is limited to specific browsers or specific computers, verify that cookies are allowed on that computer. A cookie is used to identify the computer for security reasons and blocking cookies may have unpredictable results.

                Comment


                • #9
                  Re: XHTTPRequest Error / 403 Forbidden

                  As it turns out, this problem was more involved than just performing an "Update Compiled Files for Ajax Grids, followed by a full republish after clearing the publication history."

                  It was a little complicated, but Lenny was kind enough to spend time with me and troubleshoot what I thought was a problem, but was actually a change in the design of the software regarding the security settings for grids, versus a5w pages. Thanks to him, I now have it working correctly.

                  Don if you are still having problems, let me know and I'll explain how to correct it.
                  Sergeant Richard Hartnett
                  Hyattsville City Police Department
                  Maryland

                  Comment


                  • #10
                    Re: XHTTPRequest Error / 403 Forbidden

                    Would you mind sharing what Lenny worked you through? I too am having issues with only 1 PC right now, and any clues to point me in the right direction would be appreciated.

                    Thanks,
                    Bill

                    Comment


                    • #11
                      Re: XHTTPRequest Error / 403 Forbidden

                      Okay here is what I had to do. If I don't explain it correctly, maybe Jerry or Lenny will chime in:

                      1. Go to Web Security / Web Security Configuration, and scroll down to "Customize Options."

                      2. Expand that section, then check (tic) the following items:
                      a. Enable component security for 'virtual pages.'
                      b. Always enforce security at component level for AJAX grids.

                      3. Click Okay, and return to the original "Web Security" section.

                      4. Now click on "Component Security." (This is new.) In this section, you
                      will have to set individual security rights for each Ajax enabled grid or report. (Previously we only had to set security on a5w pages, now it has to be set on individual grids and reports as well.)

                      5. After all the security settings are complete, close out of this dialog box, and republish your overall security settings. (I also republished all my pages, but I don't know if that is necessary or not.)

                      Now reopen a "problem" page and see if the XHTTP error message has disappeared.

                      It looks like the original problem stemmed from the security options being set correctly on the a5w page, but not on the actual grid, so the error message would kick in.
                      Sergeant Richard Hartnett
                      Hyattsville City Police Department
                      Maryland

                      Comment


                      • #12
                        Re: XHTTPRequest Error / 403 Forbidden

                        I don't know if this is the same issue or not. I'm using the first build before the build the created many 403 errors when trying to create a pdf report.
                        When I print from a dialog, no error. If I have a "print report" button on a grid to do the same action as in the dialog except a different pdf report, I get the 403 forbidden. I have no security on.

                        Comment


                        • #13
                          Re: XHTTPRequest Error / 403 Forbidden

                          Jerry and Rich

                          Thanks for the quick and instructive help. The Component security got me over the hump. Most all is working. Now I have a record insert with a Error 500 but that's another story for another thread. Kinda new to Alpha5 -- Loved Alpha4 -2 thru 8 though.

                          Thanks Again

                          Comment


                          • #14
                            Re: XHTTPRequest Error / 403 Forbidden

                            Thanks Rich,

                            I've gone through the motions now... not sure it has solved my issue though, but I'm sure that will help some others.

                            Seems if I let the web app sit on a page for a while, then click on a detail view, I get the error... if I reload the page then click immediately on the detail view link, no error.

                            Thanks!

                            Comment


                            • #15
                              Re: XHTTPRequest Error / 403 Forbidden

                              Is this the same error anyone else is getting? It seems to happen ONLY if I leave the page up for a while (intermittently), then click a detail view link. AND on one other users PC, can't get to a detail view page without seeing this... then the "working" message stays on screen forever... Otherwise, everything works perfectly.
                              (please see attached image).

                              Comment

                              Working...
                              X