- Daniel Fandrich found out we didn't pass on the user-agent properly when
doing "proxy-tunnels" with non-HTTP prototols and that was simply because the code assumed the user-agent was only needed for HTTP.
This commit is contained in:
10
lib/url.c
10
lib/url.c
@@ -4278,10 +4278,12 @@ static CURLcode setup_conn(struct connectdata *conn,
|
||||
lingering set from a previous invoke */
|
||||
conn->bits.proxy_connect_closed = FALSE;
|
||||
|
||||
/*************************************************************
|
||||
* Set user-agent for HTTP
|
||||
*************************************************************/
|
||||
if((conn->protocol&PROT_HTTP) && data->set.str[STRING_USERAGENT]) {
|
||||
/*
|
||||
* Set user-agent. Used for HTTP, but since we can attempt to tunnel
|
||||
* basically anything through a http proxy we can't limit this based on
|
||||
* protocol.
|
||||
*/
|
||||
if(data->set.str[STRING_USERAGENT]) {
|
||||
Curl_safefree(conn->allocptr.uagent);
|
||||
conn->allocptr.uagent =
|
||||
aprintf("User-Agent: %s\r\n", data->set.str[STRING_USERAGENT]);
|
||||
|
||||
Reference in New Issue
Block a user