 |
Post AyGpeJ6Qig8iHtU968 by [email protected] |
 |
More posts by [email protected] |
|
Post #AyGpeCZwyWas3QF7dg by [email protected] |
|
0 likes, 0 repeats |
|
|
|
After careful study of every HTTP spec and draft ever written, it appears that … |
|
|
|
Post #AyGpeCgKanhKNDEDaK by [email protected] |
|
0 likes, 0 repeats |
|
|
|
The specific behavior in Curl is a little odd. There's this CURLOPT_ACCEPT_… |
|
|
|
Post #AyGpeCn4Bl5Mi6Nb5E by [email protected] |
|
0 likes, 0 repeats |
|
|
|
In case you're wondering -- because this took me about an hour of squinting… |
|
|
|
Post #AyGpeJ6Qig8iHtU968 by [email protected] |
|
0 likes, 1 repeats |
|
|
|
@cliffle open an issue on curl, I'm sure they will be glad to see some huma… |
|
|
|
Post #AyGpeJDAJdWkcmdWb2 by [email protected] |
|
0 likes, 0 repeats |
|
|
|
@jhelou I plan to open an issue, but first I'm doing some background readin… |
|
|
|
Post #AyGpeN0CDnWuNibDw8 by [email protected] |
|
0 likes, 0 repeats |
|
|
|
@cliffle @jhelou if you can identify the code path, maybe git blame will help? |
