Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gupnp gupnp
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & 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
  • GNOME
  • gupnpgupnp
  • Issues
  • #63
Closed
Open
Created Jan 05, 2022 by Jens Georg@jensgeorgMaintainer

Potential endless loop if server returns METHOD_NOT_ALLOWED

UPnP requires the client to re-send the SOAP action with method M-POST if POST did not succeed.

However, it looks like that the client code does not check if the method was not already M-POST and if the server will return METHOD_NOT_ALLOWED as well, the client code does not check if the method already was M-POST and just keeps on re-sending the SOAP action

Edited Jan 05, 2022 by Jens Georg
Assignee
Assign to
Time tracking