Details

    • Type: Feature Request
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 3.9.0.Final, 3.8.9.Alpha02
    • Component/s: None
    • Labels:
      None

      Description

      The cache-control directive, when specified on the UI, gets too much encoding when being set as a header. This means that it's not useful at the current state when more than one parameter for the cache-control is set:

      For instance, the string "no-cache, max-age=0, must-revalidate, no-store" becomes this header:

      Cache-Control:no-cache%2C+max-age%3D0%2C+must-revalidate%2C+no-store

      The input should be sanitized only for new lines, to avoid a "HTTP Response Splitting" attack.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                juraci.costa Juraci Paixão Kröhling
                Reporter:
                juraci.costa Juraci Paixão Kröhling
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: