StArL0rd84 wrote:But... i'm just extracting a link from the xml file to use elsewhere.
The file is local so i dont need to log on for that.
Also i tried logging off youtube and it still downloaded the right file.
I'm thinking big brother Google knows my IP.
Then when i try to download the file they know it's my specific subscription box xml to generate.
Just a theory ;P
Nope. The only way this would work is if you are signed into your Google Account with Internet Explorer. Not Chrome, not Edge, not Firefox, but old-school Microsoft Internet Explorer. If you have a "cookie" from a site in IE, then WebParser, which uses calls to the IE API to work, will in fact use that cookie and the site you connect to will see you as signed in. Of course if you ever get "logged out" in IE, if the cookie expires, or some cleanup tool you use clears IE cookies, then the skin would stop working until you go to IE and sign in again.
HTTP is "stateless", there is no persistent connection maintained, and every HTTP request to a server is a brand-new, entirely anonymous thing. No matter what kind of complicated "authentication" a site uses, at the end of the day, they all boil down to some flavor of you sending an HTTP request, the site asking your browser or device "Ok, do you have a session cookie for this site, so we can know who your are?", and your browser or device answering "sure, here you go.". WebParser can't understand the question, and can't provide the answer. IE can, but that is a bad way to write a skin.
It can't be IP. First, most of us have dynamic IP addresses provided by our ISP, and they change all the time, and second, your external IP address points to your ISP, not to "you". That is why people who want to track you down by IP need to get court orders for your ISP. When you download that copy of Game of Thrones with BitTorrent, HBO is going to go to your ISP and ask "who had that IP address on this date and time?" If your ISP is any good, they won't tell HBO that, but they are likely to send you an email saying "Hey, HBO is bugging us about you, stop downloading Game of Thrones!". Even then, your external IP only points to your cable modem or router even from the view of your ISP. It's not "you" that downloaded Game of Thrones, but your little brother on this laptop. That's your story and you're sticking to it... But someone in your house did...
In any case, if we assume we lived in a world where YouTube can know that this HTTP request came specifically from StArL0rd84 in spite if the fact that they have no logical support for that assumption, parsing XML is no different than parsing anything else. It's all just "text" to WebParser. You just need to find the patterns you can search on, and capture the data you want. There really is no reason to "download" the XML and parse it as a local file that I can see. You are just downloading what WebParser already has.