I understand that some of music server are pointing to invalid ips per DNS but I think most of them does work if we can get response from a server in mainland.
I think m2 and m10 are returning invalid address when oversea but most music returned by this api is m8
Do you mean that this rule is related to the mobile apps? I haven’t checked the mobile apps but these two rules don’t match the PC web version. Still the m10 address is the main address for PC web version currently. Can you show the environment you’re in, like whether it is PC version or mobile apps, the version of mobile apps, etc.?
yes, i can confirm that this is point where iOS App and MacOS’s version are trying to connect
get music:
[02/May/2016:03:24:36 -0400] “POST /eapi/song/enhance/player/url HTTP/1.1” 200 255 “-” “\xE7\xBD\x91\xE6\x98\x93\xE4\xBA\x91\xE9\x9F\xB3\xE4\xB9\x90 3.4.0 rv:368 (iPhone; iPhone OS 9.3.1; en_US)”
[02/May/2016:07:37:24 -0400] “POST /eapi/song/enhance/player/url HTTP/1.1” 200 244 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/601.5.17 (KHTML, like Gecko)”
copyright:
[02/May/2016:03:08:00 -0400] “POST /eapi/copyright/restrict/ HTTP/1.1” 200 77 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/601.5.17 (KHTML, like Gecko)”
others, these may not need proxy
[02/May/2016:03:08:00 -0400] “POST /eapi/pl/count HTTP/1.1” 200 4284 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/601.5.17 (KHTML, like Gecko)”
[02/May/2016:03:24:38 -0400] “POST /eapi/song/lyric HTTP/1.1” 200 102 “-” “\xE7\xBD\x91\xE6\x98\x93\xE4\xBA\x91\xE9\x9F\xB3\xE4\xB9\x90 3.4.0 rv:368 (iPhone; iPhone OS 9.3.1; en_US)”
[02/May/2016:03:24:46 -0400] “POST /eapi/resource/commentInfo/list HTTP/1.1” 200 207 “-” “\xE7\xBD\x91\xE6\x98\x93\xE4\xBA\x91\xE9\x9F\xB3\xE4\xB9\x90 3.4.0 rv:368 (iPhone; iPhone OS 9.3.1; en_US)”