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

Santize Javascript ???

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

    Santize Javascript ???

    Can anybody tell me what exactly this UX property in build 7902 is doing?

    After updating from 7582 to 7902, I have a bunch of OnChange events in a UX no longer working. There is no documentation I could find on this property, the tip just says
    'In a data bound UX component, the javascript sent from the server to the client to populate controls in the UX may contain executable code. If you check this property, the javascript is encoded to disable the executable code in the response sent to the client'

    I take it this is some sort of security setting? If this is suddenly enabled by default, what other problems will this cause?

    Sanitize Javascript.jpg

    Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

    #2
    So yes, this property has killed a bunch of my javascript actions. So, now I have to go through a hundred components and figure out which are impacted and modify them.
    This is ridiculous. Properties such as this should not be introduced then enabled as the default when it IS going to break an application. I am beyond frustrated !!!
    Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

    Comment


      #3
      I hear you, and it seems to be happening fairly often lately with new default settings having big impacts on existing components.

      Just for your reference, I reported what I thought was a bug back in August, and was told this new feature is designed to prevent xss exploits.

      Comment


        #4
        Insanity: doing the same thing over and over again and expecting different results.
        Albert Einstein, (attributed)
        US (German-born) physicist (1879 - 1955)

        Comment


          #5
          This relates to a potential security issue we found when we had one of our products pen tested. The tip on the checkbox summarises it pretty well I think - essentially the idea is that unsafe code is being removed/sanitized when returned from Alpha to the browser. I could imagine it causing a problem if you stored Javascript scripts in a database and then returned those scripts to the browser to run - but that would be an exceptional case I would think?

          If the setting appears to have broken something else where you are *not* returning scripts from databases to the browser, I'd report it to Alpha as a bug.

          Hope that helps.

          Comment


            #6
            Well that's all well and good.

            I have a large, sometimes complex application that has been developed over many years. My point is, blindsiding users with a failing application after updating by turning on this type of setting by default is bad practice.
            Notifying users that there is a potential security issue and how to turn on the protection would be a much preferable approach. At minimum having an option to turn this setting on and off globally would be better than outright breaking the application.

            Nuff said on this.
            Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

            Comment


              #7
              Originally posted by iRadiate View Post
              Well that's all well and good.

              I have a large, sometimes complex application that has been developed over many years. My point is, blindsiding users with a failing application after updating by turning on this type of setting by default is bad practice.
              Notifying users that there is a potential security issue and how to turn on the protection would be a much preferable approach. At minimum having an option to turn this setting on and off globally would be better than outright breaking the application.

              Nuff said on this.
              Nani !!
              sorry for the lose , have you tried to restore back up ?

              Comment


                #8
                I haven't lost anything, except a ton of time if I decide to actually update to build 7902 and work though all the stuff it breaks. For now, I don't have the time, so I'm staying at 7582.
                Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

                Comment


                  #9
                  Originally posted by iRadiate View Post
                  I haven't lost anything, except a ton of time if I decide to actually update to build 7902 and work though all the stuff it breaks. For now, I don't have the time, so I'm staying at 7582.
                  It’s ok
                  shit happens what can you/I/we do about it
                  that’s reminds me of Microsoft Windows server
                  when they could easily just disable many security concerns on their servers yet it’s open by default

                  just like the sharing c$ to access drive from the network

                  i always thought why on earth they just didn’t disable it by default instead of wasting time & effort to find such a thing exist lol and many many many things like that
                  i totally feel you

                  Comment


                    #10
                    The sanitize javascript feature also negatively affects html editor controls. See the post HTML Editor in 7902

                    Comment

                    Working...
                    X