Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
schleuder
schleuder
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 101
    • Issues 101
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 3
    • Merge Requests 3
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • schleuder
  • schleuderschleuder
  • Issues
  • #375

Closed
Open
Opened Oct 29, 2018 by georg@georgOwner

Handle space-separated fingerprints for all relevant keywords

In version 3.2.0, we introduced spaces-separated fingerprint support for x-subscribe.

We should probably revisit this for the other relevant keywords, too. I just did x-fetch-key with such a fingerprint, and got, in return, ten times the message: Invalid input. Allowed are: URLs, OpenPGP-fingerprints, or email-addresses.. I'm not sure, and didn't checked, if this is an issue for other keywords too, but I guess so.

OTOH, as we spoke about "being implicit", I wonder if parsing fingerprints with spaces is maybe error prone?

Still, if we do, we should be consistent. Tagging this for 4.0 for now, and labeling as bug.

Any opinions?

Assignee
Assign to
Future
Milestone
Future
Assign milestone
Time tracking
None
Due date
None
Reference: schleuder/schleuder#375