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

v11 Prevent HTM Files on alpha server from caching in user's browser

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

    v11 Prevent HTM Files on alpha server from caching in user's browser

    Hello,

    I am new to alpha. I developed a Help system which is web based. The HTML files/images are on the alpha server. I have a Help button in my alpha application which is linked to my index.htm. We added the htm/html files to the alpha server and I opened the main page, index.htm. The newest help content loaded just fine for me and included the changes I had JUST made. However, a coworker launched the same index.htm page and received the old version, I'm assuming because his browser brought up a cached version.

    After that incident, I have included code between the <HEAD> tags in each HTML file to include a file with HTML <head> tags to not cache pages - see below code snippet.
    Code:
    <!--#include file="RefreshNoCache.html" -->
    In RefreshNoCache.html, I'm using the following code:

    Code:
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <META HTTP-EQUIV="Cache-control" CONTENT="no-cache">
    <META HTTP-EQUIV="Pragma" CONTENT="no-cache">
    <META HTTP-EQUIV="Expires" CONTENT="-1">
    </head>
    </html>
    I was told by local IT that in addition to the above code, we need to also set the CacheControlCustom property in IIS to 'no-cache' for pages we don't want cache as that will add an HTTP header for cache-control in the document. I am told by our alpha developer that she is not sure how to do this since we are not using IIS, we are using Alpha APP Server to host the application.

    Any ideas? My only other idea is to host the web-based Help HTM/HTML files on our SQL server which IS running IIS and just link to THAT location rather than location on the alpha APP server.

    Your help is MUCH appreciated!

    #2
    Re: v11 Prevent HTM Files on alpha server from caching in user's browser

    Try this in your head section

    <META HTTP-EQUIV="Cache-Control" CONTENT="no-cache" />
    <META http-equiv="expires" content="0" />
    Frank

    Tell me and I'll forget; show me and I may remember; involve me and I'll understand

    Comment


      #3
      Re: v11 Prevent HTM Files on alpha server from caching in user's browser

      You can add the following to the top of your a5w page which will add no cache commands to the response headers.
      Code:
       <%a5 Response.NoCache() %>
      Another option which is what I have switched to on my custom pages that do not use A5 AJAX grids or dialogs but will work for both is to append a unique variable to the end of the URL string. I just append a timestamp, for example: yoursite.com/page.a5w?timeStamp=20120825012545

      You can generate this timestamp with the following xbasic:
      Code:
      val(cdate(date()) + time("0h0m0s"))
      The benefit to this method is all other included files such as images, js, and css files will remained cached but the a5w page content will reload every load.
      Last edited by LukeS; 08-25-2012, 05:07 AM.

      Comment


        #4
        Re: v11 Prevent HTM Files on alpha server from caching in user's browser

        If you are running a pre-release build after 2804, there is an option to automatically add no cache to every request that requires login. That includes html files and Ajax callbacks if they require login. The option shows in the security setting in the Customize section. If a request is always allowed, it is assumed the content probably isn't time sensitive so no cache won't be applied automatically, but any of the methods suggested by Frank and Luke will work.

        Comment


          #5
          Re: v11 Prevent HTM Files on alpha server from caching in user's browser

          <!--#include file="RefreshNoCache.html" --> is ASP code and will do nothing in the Alpha server. Your RefreshNoCache.html is not being included as you think it is, so none of the meta tags are being set into your HTML document. Alpha does not have a method for including files in static documents (*.htm, *.html), so you will have to directly place the desired tags directly in each document.

          If you use A5W pages instead of static HTML documents, then you can use Response.NoCache() and/or set any other Response headers as desired.

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

          Comment


            #6
            Re: v11 Prevent HTM Files on alpha server from caching in user's browser

            Thank you all so very much for your replies. I am going to go with the following solution by putting the below in the head section of all htm/html files for my web help:

            <META HTTP-EQUIV="Cache-Control" CONTENT="no-cache" />
            <META http-equiv="expires" content="0" />


            Thanks again, I really appreciate your help!

            --Kristin

            Comment

            Working...
            X