Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • ITS ITS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ITS - Intelligent Transport SystemsITS - Intelligent Transport Systems
  • ITSITS
  • Issues
  • #18
Closed
Open
Issue created Aug 27, 2019 by Szilveszter TÓTH@toths

HTTP 1.1 status reason-phrase (status text) is optional

Dear ETSI Team,

We had an issue with the ITS testing tool on branch STF525.

Namely, it expects the reason-phrase to be present, which is optional according to RFC 7230 (https://tools.ietf.org/html/rfc7230#section-3.1.2):

The reason-phrase element exists for the sole purpose of providing a textual description associated with the numeric status code, mostly out of deference to earlier Internet application protocols that were more frequently used with interactive text clients. A client SHOULD ignore the reason-phrase content.

 reason-phrase  = *( HTAB / SP / VCHAR / obs-text )

(The asterisk there means that it may not appear at all.)

Some HTTP server implementations now omit this part of the status line, barely emitting

HTTP/1.1 200 

(with no "OK" at the end).

The testing tool would fail with an error log like this:

MTC@13cb672994ff: Matching on port httpPort .response.statustext := "" with "OK" unmatched: First message in the queue does not match the template:

We had to change the web server implementation to include the reason-phrase to pass the test.

Thank you for your help!

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking