• SEARCH
  • DOWNLOADS
  • MY ACCOUNT
  • Buy (0)
  • CONTACT
  • Free Trial
Wowza Logo
  • PRODUCTS
  • DEVELOPER
  • SOLUTIONS
  • PRICING
  • RESOURCES
  • SUPPORT
  • My Account
  • Buy (0)
  • SEARCH
  • Ask a question
  • Forums
    • Wowza ClearCaster
    • Wowza Streaming Engine
    • Wowza Streaming Cloud
    • Wowza Player
    • Wowza GoCoder SDK
    • Wowza Developer Dojo
    • Topics
    • Questions
    • Articles
    • Users
    • Badges
  • Sign in
  • Community Home /
  • Wowza Streaming Engine /
  • General Forum /
avatar image
Question by F Lippes · Jun 02, 2009 at 01:37 PM ·

Using Content-Base from Describe

I'm running into a problem.

we created a tool that inserts some security based on parameters in rtsp urls.

it accepts urls like

rtsp://<ip>:554/sdpfile.sdp?secret=<secretstring>&client_id=<clientidentifier>

On a DESCRIBE request by wowza we return the following content-base:

rtsp://<ip>:554/sdpfile.sdp

Wowza however, continues to use the url with the parameters, but at some time it adds /trackID=n

rtsp://<ip>:554/sdpfile.sdp?secret=<secretstring>&client_id=<clientidentifier>/trackId=n

but we expect rtsp://<ip>:554/sdpfile.sdp/trackId=n

our security protocol fails, because basically the trackID=n is appended to the client identifier

Why doesn't wowza use the content-base url returned from the DESCRIBE ?
Comment

People who like this

0 Show 0
10 |600 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

2 Replies

· Add your reply
  • Sort: 
avatar image

Answer by Charlie Good · Jun 02, 2009 at 09:15 AM

If the stream name is an url as it is in this case then the query parameters are considered part of the url and not part of the stream name. The best I can do for now is fix it so the SETUP RTSP calls look like this:

rtsp://<ip>:554/sdpfile.sdp/trackId=n?secret=<secretstring>&client_id=<clien tidentifier>

rather than this:

rtsp://<ip>:554/sdpfile.sdp?secret=<secretstring>&client_id=<clien tidentifier>/trackId=n

Does this help?

Charlie
Comment

People who like this

0 Show 1 · Share
10 |600 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image F Lippes · Jun 04, 2009 at 09:29 AM 0
Share
I believe it was good practice to use the content-base when provided.

A post in another forum says:

"The new versions of the RTSP spec have clearer

language about this and mentions that the best way to figure out the URI is

to look at:

1. Content-base

2. Content-Location

3. Original URL"

Anyway, the suggested fix is cleaner then the current append of the trackID.

We have created an exception in our code to deal with the current situation.

Thanks for the quick reply !
avatar image

Answer by Charlie Good · Jun 04, 2009 at 03:13 AM

The code with the fix I proposed is here:

http://www.wowza.com/downloads/WowzaMediaServer-1-7-0/WowzaMediaServerPro1.7.0-patch9.zip

Charlie
Comment

People who like this

0 Show 0 · Share
10 |600 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Your answer

Hint: You can notify a user about this post by typing @username

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Follow this Question

Answers Answers and Comments

1 Person is following this question.

avatar image

Related Questions

URL missing - playlst.m3u8 - VLC 3 Answers

Android 4.1.1 and RTSP 3 Answers

Stream not found before onHTTPSessionCreate 1 Answer

Question: Secure RTSP , Play/Pause API/Trigger method for HLS 1 Answer

Android not able to stream .mp3 file from wowza server 2 Answers

Hot Topics
  • AWS Hosting
  • Mobile SDK
  • Deployment Options
  • Load Balancing
  • Content Security
Product Sign-in
  • Wowza Streaming Cloud
  • Wowza Player
Under the Hood
  • Developer Tools
  • Wowza System Status
  • Test Players
  • Developer IDE
Resellers
  • Find a Reseller
  • Reseller Portal
  • Become a Reseller
Company
  • About Us
  • Blog
  • News
  • Events
  • Careers
  • Customers
  • Partners
  • Contact Us
Stay Connected
Get Monthly Newsletter
Select a Language
  • English
    • English
    • Español
    • 日本語
    • 한국어
    • हिन्दी भाषा
    • 中文
    • русский язык

© 2005–2019 Wowza Media Systems, LLC. All rights reserved.   Terms | Privacy | Trademarks | Legal


Enterprise
Social Q&A

  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Create an article
  • Forums
  • Wowza ClearCaster
  • Wowza Streaming Engine
  • Wowza Streaming Cloud
  • Wowza Player
  • Wowza GoCoder SDK
  • Wowza Developer Dojo
  • Explore
  • Topics
  • Questions
  • Articles
  • Users
  • Badges