javascript - Prevent disk caching of HTML5 canvas tag for drawImage in RAP -

Use of HTML 5 canvas tags to draw images in a canvas is done on the client side Does the way.

Say eclipse is used on server side images by & lt; Your Work Space & gt; Metadata \ .plugins \ org.eclipse.rap.tools.launch \ & lt; Your Choices Confight & gt; \ .metadata \ .plugins \ org.eclipse.rap.ui \ context \ rwt-resources \ generated \ / code>.

But all of these images are also cached on the disk on the client side. These stored hex dumps can be easily used. But for security constraints they should not be cached, respectively, should be cached in memory.

Then I:

• Edited the index which was not crap because I did not want this file but the transferred images have to be cached.
• Tried to edit the GET header, but it was found that GET was already correctly modified
• tried to edit the post headers, but it found out that Post by definition does not cache anything until this Is not specifically defined which is not the case here
  • cf RFC: 2616 section: 9.5 subject:
  • Check that this problem
  • Check it relates to the application cache of HTML5

    but I do not have anything in the RAP client Nothing was found and nothing was found in the HTML 5 document for specific items related to the problem. So my question is, do you have any idea how I can change the behavior of caching images using the HTML5 canvas object in relation to RAP.

    Update # 1

    Yes ralfstx , GC.drawImage (Image) canvas using Is used to draw pictures. Please take a look at the following screenshots. When you pull an image and reach the browser cache, you will see. We only ensure that the image is closed by shutting down the server address server.

    

    If you want to see who The C image is actually pasted all of the content (CTRL + A & RAW Paste Data inside the CTRL + A & CERS) in this session copy and paste it.

    Update # 2

    The progress of the customer is not cached on, but on the server side.

    I think you use the method GC DRAWRY image to attract your images in the canvas. Whenever you create a SWT image , the file is created on the server in context / rwt-resources / generated / since the same image used from different places So this file is not clean (see).

    Update

    Sorry, I remembered that you are talking about browser cache Of course, even the browser Images will cache We can not currently stop it because the images are registered as static resources and servlet is distributed by the container and we can not control the cache header.

    As an alternative solution, you embed your sensitive images and embed them using it. SWT images plan to wrap those external resources. If you are interested, please file the file.