Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RCVR-453 SONY 2021 and 2022 - User Agent Value (Anomaly) #1228

Open
sharonmkelley opened this issue Jan 28, 2025 · 4 comments
Open

RCVR-453 SONY 2021 and 2022 - User Agent Value (Anomaly) #1228

sharonmkelley opened this issue Jan 28, 2025 · 4 comments
Labels
bug Something isn't working

Comments

@sharonmkelley
Copy link

Description

While testing OTT via RMP on Sony 2022 receiver, we have noticed an anomaly with User Agent values reported by the receiver. One value is different.

Receiver Details
KD-43X80K
PKG6.6070.0711NAA

User Agents values recorded:

192.168.2.126 GET /vod/fiat/manifest.mpd {
'user-agent': 'Dalvik/2.1.0 (Linux; U; Android 10; BRAVIA 4K VH21 Build/QTG3.200305.006.S272)',
host: '192.168.2.100:8001',
connection: 'Keep-Alive',
'accept-encoding': 'gzip'
}
192.168.2.126 GET /vod/fiat/manifest.mpd {
'user-agent': 'Dalvik/2.1.0 (Linux; U; Android 10; BRAVIA 4K VH21 Build/QTG3.200305.006.S272)',
host: '192.168.2.100:8001',
connection: 'Keep-Alive',
'accept-encoding': 'gzip'
}
192.168.2.126 GET /vod/fiat/manifest.mpd {
'user-agent': 'Atsc3TunerInputService/1.10.0_Q (Linux;Android 10) ExoPlayerLib/2.10.2',
host: '192.168.2.100:8001',
connection: 'Keep-Alive',
'accept-encoding': 'gzip'
}
Add any other context about the problem here.

@sharonmkelley sharonmkelley added the bug Something isn't working label Jan 28, 2025
@sharonmkelley sharonmkelley changed the title RCvR-453 Sony 2021 and 2022 - User Agent Value (Anomaly) RCVR-453 SONY 2021 and 2022 - User Agent Value (Anomaly) Jan 28, 2025
@sharonmkelley
Copy link
Author

Adam Goldberg
January 22, 2025 at 1:55 PM

A broadcast Application requests AMP and RMP URLs to the receiver. Therefore the Media Player Accessing Content should use the correct UA.

A BA asks the receiver to play content; the media player is playing content because the BA asked, but the “HTTP requests from the receiver” are not “on behalf of a Broadcast Application”.

For DRM Licenses the A3SA has a required to use the A331 for the UserAgent.

No argument, and we’re doing this now.

For the signalling request, I have suggested this change to Mike Dolan to include. So an ATSC 3.0 device accessing resources related to ATSC 3.0 should use in principle the A331.

Not completely sure what this means, but we would oppose a requirement that every HTTP request related to ATSC 3.0 use the A/331 user agent string.

Edit

Delete

Raj Patel
January 21, 2025 at 9:48 AM

@adam Goldberg HTTP requests from the receiver on behalf of a Broadcast Application,

A broadcast Application requests AMP and RMP URLs to the receiver. Therefore the Media Player Accessing Content should use the correct UA.

For DRM Licenses the A3SA has a required to use the A331 for the UserAgent.

For the signalling request, I have suggested this change to Mike Dolan to include. So an ATSC 3.0 device accessing resources related to ATSC 3.0 should use in principle the A331.

Edit

Delete

pete.vanpeenen
January 8, 2025 at 6:27 AM

User Agent should include software version … but I don’t see that on any of the Sony TV user agents.

latest from our 2023:

{"date":"2025-01-07T12:45:24.132Z","response":"ATSC3/2021-03 (0509 050A 050B 050D & & &; Sony; XR-55A95L; WWA; com.sony.HE.G5) Mozilla/5.0 (Linux; Android 11; BRAVIA 4K; HbbTV/2.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.77.34.5 Safari/537.36 NFBE/3.90.0.93 Model/Sony-BRAVIA-TODO","request":"${navigator.userAgent}"}

Edit

Delete

Adam Goldberg
November 16, 2024 at 2:19 PM

The specification is in A/331, and it says

7.1.2.4 HTTP User-Agent Header Field In order for HTTP servers to customize the delivery of apps, HTTP requests from the receiver on behalf of a Broadcast Application, including the launch URL request, shall provide a User-Agent header field as defined in HTTP [32] and this section. The syntax shall conform to HTTP [32] Section 5.5.3 and the syntax defined below: “ATSC3/”[-mm] “(“; ; ; ; ;[ hardwareVersion]”)”

Edit

Delete

Adam Goldberg
November 15, 2024 at 12:30 PM

Raj, can you please point at the specific text which says that in A/344.

Edit

Delete

@Selamu33
Copy link

Great and perfect Involving

@ghost
Copy link

ghost commented Jan 28, 2025 via email

@ghost
Copy link

ghost commented Jan 28, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants