Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gst-rtsp-server
gst-rtsp-server
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 83
    • Issues 83
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 10
    • Merge Requests 10
  • 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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gst-rtsp-servergst-rtsp-server
  • Issues
  • #2

Closed
Open
Created Jun 18, 2013 by Bugzilla Migration User@bugzilla-migration

problem with authentication for tunneled clients

Submitted by Alexander Schrab

Link to original bug (#702548)

Description

When clients tunnel rtsp over http, the gst-rtsp-server is handed a socket in gst_rtsp_server_transfer_connection. The authentication is however not handled correctly, it will be handled just like for non-tunneled clients and as far as I understand there will be no more authentication after the tunnel has been set up?

If this is the case, that rtsp-server should not bother itself with authentication in the tunneling case, then adding:

gst_rtsp_client_set_auth (client, NULL);

in gst_rtsp_server_transfer_connection might be sufficient (works for me, but I cannot judge if there are more use cases).

Version: 1.x

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None