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
Parse Shoutcast ICY HTTP responses #1151
Comments
See: #595 (comment) |
vinniefalco
changed the title
Http client with customized response
Parse Shoutcast ICY HTTP responses
Jun 7, 2018
Let me spend a little time on this today and see what I can do |
vinniefalco
added a commit
to vinniefalco/beast
that referenced
this issue
Jun 10, 2018
fix boostorg#595, fix boostorg#1151 This provides a stream filter which converts the ICY HTTP response handshake at the beginning of a stream to HTTP/1.1.
Please try the develop branch which has version 173. The class
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am currently using boost::beast to implement a ntrip 1.0 client. It has the request like:
GET /BUCU1 HTTP/1.0 User-Agent: NTRIP GNSSInternetRadio/1.2.0 Authorization: Basic aHVnb2JlbjpodWdvYmVuMTIz
And the response is like: ICY 200 OK
It has the non-standard http response.
I use the beast http client example code, it get this response in the buffer. But it generates a exception in the read function. The error is "Read, Bad version". I am wondering what is the best way to handle the non-standard http response.
void
on_read(
boost::system::error_code ec,
std::size_t bytes_transferred)
{
boost::ignore_unused(bytes_transferred);
}
The text was updated successfully, but these errors were encountered: