Uploaded image for project: 'ngrinder'
  1. ngrinder
  2. NGRINDER-573

Make cookie parsing impl work with secure=1 entry

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.2
    • Fix Version/s: 3.1.3
    • Component/s: controller
    • Labels:
      None

      Description

      Current Cookie parsing doesn't recognize secure=1 entry.
      AFAIK, "secure" entry should be formed "secure", not "secure=1",
      but some web server emit secure=1 for cookie and the other tool "loadrunner" handles secure=1 entry well. Some users already complaint about it.

      http://ngrinder.642.n7.nabble.com/Post-td462.html

        Activity

        Hide
        junoyoon JunHo Yoon added a comment -

        Fixed. I changed Cookie class to ignore secure=1, BLARBLAR; pattern.
        And I located it in the grinder patch lib

        Show
        junoyoon JunHo Yoon added a comment - Fixed. I changed Cookie class to ignore secure=1, BLARBLAR; pattern. And I located it in the grinder patch lib
        Hide
        junoyoon JunHo Yoon added a comment -

        Close All

        Show
        junoyoon JunHo Yoon added a comment - Close All

          People

          • Assignee:
            junoyoon JunHo Yoon
            Reporter:
            junoyoon JunHo Yoon
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: