clamp-orchestrator / clamp-core

A microservices flow orchestrator and workflow manager.
https://clamp-orchestrator.github.io/clamp-orchestrator/
MIT License
9 stars 4 forks source link

Workflow step fails if workflow is triggered with a specific user agent string #88

Open priyaaank opened 3 years ago

priyaaank commented 3 years ago

Describe the bug When the initial workflow is called with following header and value, then the parsing before the first step fails. Header name: User-Agent Header value: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20100101 Firefox/16.0

To Reproduce Steps to reproduce the behavior:

  1. Create any workflow
  2. Trigger workflow and ensure that above specified header is part of the trigger request
  3. Check the service request status

Expected behavior Expected to see a successful execution of the step

Screenshots/Logs However, this is the error I see

{
    "service_request_id": "a28ad6ed-1101-4909-9132-54ecf08622ba",
    "workflow_name": "benchmarking_http_services_flow",
    "status": "FAILED",
    "total_time_in_ms": 3,
    "steps": [
        {
            "id": 1,
            "name": "benchmarking step one",
            "status": "STARTED",
            "time_taken": 0,
            "payload": {
                "request": null,
                "response": null
            }
        },
        {
            "id": 1,
            "name": "benchmarking step one",
            "status": "FAILED",
            "time_taken": 4,
            "payload": {
                "request": null,
                "response": {
                    "errors": {
                        "code": 400,
                        "message": "Get \"http://api-server:8083/api/step1\": net/http: invalid header field name \" rv\""
                    }
                }
            }
        }
    ],
    "reason": ""
}

Desktop (please complete the following information):

Additional context None