Details

    • Type: Bug
    • Status: Closed
    • Resolution: Inactive
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
      r36691
    • Branch Version/s:
      5.2.x

      Description

      The default order of filters is defined in the portal web.xml for the liferay and in the speed_filters.xml for portlets deployed from war.

      I wonder why the ETag filter is the last one here. ETag should be able to respond with 304 even for cached data, or the cache should do the same? Otherwise cached data is always served completely with 200, however the ETag filter could prevent this.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                8 years, 40 weeks, 5 days ago