MITM HTTPS connections parsing request bug
First of all great job. I love goproxy!
I came across a bug after i managed to get MITM and HTTPS hijacks working.
It seem's like some requests are parsed incorrectly. Likely an easy issue to fix, but im not entirely sure how the requests are parsed.
The error is: Cannot read TLS response from mitm'd server http: invalid method "skin=default&skinLoaderChecksum=&isAjaxRequest=true&x=0.
As you can see the HTTP method is actually the POST data for some reason, this is only happening when certain characters are inside the post data so i expect its to do with formatting.
I logged the request (fmt.Println(req)) and you can clearly see the POST params are appended to the HTTP METHOD for some reason, which of course results in the above error.
&{v=r20170213115309&reason=fi&bcr=%5B940116767%2C1958053874%2C50117821%2C-990935 407%2C1335944403%2C-578110537%2C-1369062603%5D&c=03AI-r6f7MJCx9cyRI97j_DhMGp9V_i CSmslrbwWpEMiUfCUBEHLtF-W4kYFSFqzg_ax9ntszM7glIuJgVhjQnubU795mSc__u2XnWG2CFNXJrw AvTUxpatkMIisNL8aJaUQfg8SQAkusKiffRjS4ba9q9kNqIL0b_UapFDlrEWgjl03Y-4oqxE7VeuhLev HMcxE3xJ2pvvjHK5Z9mz92EgJzKrTf-pE_jaKYGzjBhij__0oxWY_rttJ0j8guhGi_IHY_Al7_i-puGK og1q2n9Ug4XoTHohcw3S-2NkOzNnbzv5LBVM38L3z7JLCo8dWui-CVzOG5FjiKTpiHur_VzFgmi5-Uep 4qKfvaRBX7CmWzO2fgF494wKXINM5e_uPQy7eTwDypoxNjwhXGuB_xNclpwMXzsbDr6dw&chr=%5B64% 2C33%2C29%5D&hr=-2050953731&bg=!PTugOxpHw6xYJodDSDJBvJPX7kBt33oHAAAAG1cAAAAVnASb s0Lc-YlXKeetq-Bs9F5ae_1aMu2W_9JtEaSDF2zKWLv-VDYdQvE-AJzHhU-q86PMf7tAtLQJSbZWq4d5 J3mCZvKsPAiLHa1CSlJPduxnTI7DmCfZ8FJ3rTjcLxv3ZvC9p9QCh4qrpG1QtRR8mWKFMqrD1OV23O69 iwPdMuIPoZeMOfvelFUXgH6ZzVvWXanb9RJHZDuH-dQDPKYJQkJ9qADqDRSw7VZa_ZlLFbKYp51BJBCw z8rrgQz_FI3PX-eI2kljDgZYIO_P05sDWLOxEr0y_bBbEF8v95VdUB-vowMtGDGEl4qKE_xBHkyNDmie BroEQoUc8Bkc3hebkIAKTGtBIAbvWTBf4Z56yTja8GCtvok9phaJGlV1Ysy7beTF3QJdhKRU0OE6LPZO T4dy4ko-MDq0XDMDBzcw5sFHKsCGfIzYkPRCeW9B_8jgyF_OzqtB4cuFav24bnW76bldCukKchNPdi1j hakJQeMBF8pbZ5NC5K8Nouc5HkXw5H3S1aHv_ywM4HXEL0bcCqEU1LjrnJNBCSegPy4C6pVZAZSi328O SEllnWNOW9So8QaRE-xfKWVLzZ4XUvWe86AJgsMU8gdczFoDL8kR3SP0GIeyerix26_lj6z50Jzxoyxr svPmBCJz_O90CofQzdLSjuKHfaxikFsog1YPna_1MTFB1H_q4yEhibMvlbHXll6FIx3AMOKyrvcE-o3I dsxtMzcMtkYhjPksQuwwFtCg86hYqee0knFGxb4xpuo_mB0nkYSxd0AC8tymRl79grTBlfWnGLHnQesv ndCNMIVxLwaarp_ifFzpAfOOtLAkcHN6qd2iVGVZV9wR5ios-e0sLsQnUaEmiGL0PfFEeDpVKPRMwuYS quMxjlMrtbobYlRpcXxQ9wQY9QP8eJQccV3mxlSPgUIyu34aUq2TiTT57JT_W7Kjtd2besPeHeWLVQXk rA6lvSun7YYriBrO1rBtVx3Mh6QjMqCKi4Bon05vOLqD-gf14mL3Ou9NjhiaV6ebTW2WjkJ9uNIkk1Iq 1PSQkHyzr_VJUqwT980PXfYxncL-yUWEdSJVr5d0zcrluneNgibXI94S4KyYgAMMWlBQV9UlgfsAj3Gd 9sWYtahtlAcgBOH1zE8dlRm2-iR9eCtFph4L6qXyPiME0kbEswQSVtr4vr5EHQWX808xMV0nyNpHxvSe vq43q_5BOrrV7at2E-gIy5g_Qooj6g2qTbi5YJqdu4UuctGKAbf91xvpFZCL257Ry6e24H77-vuKgHel WPa9pedaYuwTgquR1G5xu6_xACbP4AsOi9GHTlJnjnxvDghSdGWvfwhqG9G1zf1EBYS_T78mUEfZ6wHf f2VKIG_jut7qOoArKjF7r7V9cUVu1jtqt7_ayAR4znXrkdfqe_WdBZQT4YmDqgT9IPXf8veHbg1xzm23 R0HE9Gj2kt0OthA9ertXzQHQjwpynvcbiFTitRo1Y9qmWJk4VogFvI2sSmMxJx1WF-tZkT5wYaROa9ot TvkuRm2t2Jp_5I5nK8-7tF15m5YTG3za3MnxAEfQZcxYB7JQLbyZPOST https://www.google.com: 443/recaptcha/api2/reload?k=6Le4AQgUAAAAAABhHEq7RWQNJwGR_M-6Jni9tgtA HTTP/1.1 1 1 map[Origin:[https://www.google.com] Cookie:[NID=88=P0HULANn_DRR--prgn3SNfNBuAM KUIfeXBntMPgwarzIq80jhC7Ur5Ybe0peGUKrlcsy0OJy9JMDmv2fWELUOhcDE6zDUPpREj_pBPvt7mG RLuCDyey9iMHWwCTDuIOX] Accept:[/] Proxy-Authorization:[Basic ZWFzeTplYXN5] Acc ept-Encoding:[gzip, deflate] Accept-Language:[en-gb] Content-Type:[application/x -www-form-urlencoded;charset=UTF-8] User-Agent:[Mozilla/5.0 (iPhone; CPU iPhone OS 10_2 like Mac OS X) AppleWebKit/602.3.12 (KHTML, like Gecko) Version/10.0 Mob ile/14C92 Safari/602.1] Connection:[keep-alive] Referer:[https://www.google.com/ recaptcha/api2/bframe?hl=en&v=r20170213115309&k=6Le4AQgUAAAAAABhHEq7RWQNJwGR_M-6 Jni9tgtA] Content-Length:[2210]] 0xc08225cc80 2210 [] false www.google.com map[] map[]
map[] 81.136.252.148:55249 /recaptcha/api2/reload?k=6Le4AQgUAAAAAAB hHEq7RWQNJwGR_M-6Jni9tgtA }
Would be greatfull if someone could help and try to track down the bug.
Is this issue still present?