Details

    • Release Notes Text:
      Hide
      PROBLEM: For simulation the problem, it's sufficient to point browser to http://localhost:8080/portal/classic and log all HTTP requests sent by browser. It can be seen that HTTP requests for obtain images (*.jpg, *.gif, favicon.ico, ...) are repeated during each HTTP request to portal page and HTTP response contains header "Cache-control: no-cache" for all images. This is bad from performance perspective on server side (more request for images needs to be processed by server) but also from client side (Images needs to be received from server to client after each HTTP request to portal page, which is bad for bandwidth as network is more burdened because of this).

      CAUSED BY: Problem is caused by incorrect mapping of staticResource handler in controller.xml . StaticResource handler is mapped after PortalRequestHandler, which means that all images are firstly processed by PortalRequestHandler. This is non-sense and it results that incorrect HTTP header "Cache-control: no-cache" is used for images and some non-sense operations are called (like calling DataStorage.getPortalConfig with argument "favicon.ico" ).

      SOLUTION: Thing is that images should be processed only by StaticResourceHandler and not by PortalRequestHandler at all. So I changed the order in controller.xml configuration, and I've added StaticResourceHandler before PortalRequestHandler (it was opposite before).
      Show
      PROBLEM: For simulation the problem, it's sufficient to point browser to http://localhost:8080/portal/classic and log all HTTP requests sent by browser. It can be seen that HTTP requests for obtain images (*.jpg, *.gif, favicon.ico, ...) are repeated during each HTTP request to portal page and HTTP response contains header "Cache-control: no-cache" for all images. This is bad from performance perspective on server side (more request for images needs to be processed by server) but also from client side (Images needs to be received from server to client after each HTTP request to portal page, which is bad for bandwidth as network is more burdened because of this). CAUSED BY: Problem is caused by incorrect mapping of staticResource handler in controller.xml . StaticResource handler is mapped after PortalRequestHandler, which means that all images are firstly processed by PortalRequestHandler. This is non-sense and it results that incorrect HTTP header "Cache-control: no-cache" is used for images and some non-sense operations are called (like calling DataStorage.getPortalConfig with argument "favicon.ico" ). SOLUTION: Thing is that images should be processed only by StaticResourceHandler and not by PortalRequestHandler at all. So I changed the order in controller.xml configuration, and I've added StaticResourceHandler before PortalRequestHandler (it was opposite before).
    • Release Notes Docs Status:
      Not Yet Documented
    • NEEDINFO:
      Nobody

      Description

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  mposolda Marek Posolda
                  Reporter:
                  mposolda Marek Posolda
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: