Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D Demonstrator - Reasoning WebAPI
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • cogsys
  • Dare2Del
  • Demonstrator - Reasoning WebAPI
  • Issues
  • #30

Closed
Open
Created Nov 26, 2020 by Sebastian Seufert@sebastian.seufertMaintainer

'Request zero' at GET

API reacts with completed request 0.

/*Thu Nov 26 14:04:59 2020*/ 
request(1, 1606395899.985, [peer(ip(127,0,0,1)),method(get),request_uri('/bg'),path('/bg'),http_version(1-1),content_type('application/json'),user_agent('PostmanRuntime/7.26.8'),postman_token('fc04c4f5-3f71-40a2-b3fe-66fc358a9f10'),host(localhost),port(5000),content_length(735)]).
completed(1, 0.029408105, 630, 200, ok).

completed(0, 0.047579236, 328, 400, error("Illegal HTTP parameter:   { (in_http_request)")).

server(stopped, 1606395987).

I have no idea at the moment what causes this / where this comes from, but since it does not crop up in Postman or curl, I assume this should not interfere with API functionality from the clients perspective.

Investigating.

Edited Nov 26, 2020 by Sebastian Seufert
Assignee
Assign to
Time tracking