Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
M
Minipots
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Turris
  • Sentinel
  • Minipots
  • Issues
  • #49

Closed
Open
Opened Nov 23, 2020 by Miroslav Hanak@mhanakMaintainer

Make `user_agent` field optional part of the Sentinel message

User agent header is optional part of HTTP message. Currently user_agent field is sent to server every time even there was no user agent header or the header had an empty value.

To distinguish these there are a few options:

  1. don't send user_agent field when there is no header, send empty user_agent value when header has an empty value

  2. send msg_pack nil value in user_agent field value, send empty user_agent value when header has an empty value

  3. don't send user_agent field when there is no header or the header value is empty

Seninel_meeting_w48

@mprudek @vmyslivec @kkoci

Edited Nov 23, 2020 by Martin Prudek
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Turris OS 5.2.1
Milestone
Turris OS 5.2.1
Assign milestone
Time tracking
None
Due date
None
Reference: turris/sentinel/minipot#49