Handle Content-Type header with charset information

Merged Tomasz Maczukin requested to merge fix/content-type-with-charset-handling into master

What does this MR do?

Adds support for Content-Type header with charset part, e.g. `Content-Type: application/json; charset=utf-8".

Why was this MR needed?

If GitLab server is sending Content-Type with charset information, communication is failing with an error: Server should return application/json. Got: application/json; charset=utf-8 PANIC: Failed to register this runner. Perhaps you are having network problems. Please read #2000 (closed) for a reference.

Are there points in the code the reviewer needs to double check?

Does this MR meet the acceptance criteria?

  • Documentation created/updated
  • Tests
    • Added for this feature/bug
    • All builds are passing
  • Branch has no merge conflicts with master (if you do - rebase it please)

What are the relevant issue numbers?

Fixes #2000 (closed)

Merge request reports