Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-27366

Fix duplicate content-type header in gatling tests

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 10.10
    • Fix Version/s: 10.10-HF08
    • Component/s: Performance, Tests
    • Tags:
    • Sprint:
      nxcore 11.1.10
    • Story Points:
      2

      Description

      When running Sim25BulkUpdateFolders and tracing request we can see that the content type header is duplicate (2 times the same value application/json).
      This can be rejected as a bad request by different proxies, for instance apache can reply with a 400 Bad request with an html body:

      <!doctype html><html lang="en"><head><title>HTTP Status 400 – Bad Request</title><style type="text/css">h1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} h2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} h3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} body {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} b {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} p {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;} a {color:black;} a.name {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 400 – Bad Request</h1></body></html>
      

      resulting in parsing error on gatling side:

      The current character read is '<' with an int value of 60
      Unable to determine the current character, it is not a string, number, array, or object
      line number 1
      index number 0
      <!doctype h ....
      

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 5 hours
                5h

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.