Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-plugins-base gst-plugins-base
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 642
    • Issues 642
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 80
    • Merge requests 80
  • 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
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamerGStreamer
  • gst-plugins-basegst-plugins-base
  • Issues
  • #365
Closed
Open
Issue created Jul 08, 2017 by Bugzilla Migration User@bugzilla-migration

Rtsp-over-http includes port 80 in internal uri

Submitted by Jeff Shanab

Link to original bug (#784703)

Description

I am having trouble using the rtspsrc for rtsp-over-http that I am starting to think is a bug. Setting protocols and/or setting rtsph does not open a socket to port 80. I am forced to actually put ":80" in the uri. When I do it ends up in the uri posted and the device does not respond. This is contrary to the standard, the device should not see the port 80 in it's url. Multiple devices tested using live555 and curl without issue.

Tested with gst-launch on gstreamer 1.12 on windows x64 but primary usage is from c++ program.

Is this latest?, I am finding terribly outdated documentation and broken links on https://gstreamer.freedesktop.org/

Version: 1.x

Assignee
Assign to
Time tracking