Is it inadvisable to use http traffic analysis to build a meta web service / pseudo-api? -
I'm looking at the HTTP traffic analyzer which is browser add-on that monitors and analyzes incoming and outgoing HTTP traffic between the browser .
* Requests and feedback headers * Send and received cookies * Query parameter parameters * Post parameters * Response body
My question is whether this web To make use of the service it is understandable.
The interest I am using is using Windows SkyDiv - which provides 25GB of storage as a storage solution for my web app.
So what I'm thinking is using HTTP traffic analysis to find out how to duplicate my web application interacting with my browser SkyDrive account.
Is this a bad solution? I'm finding that one of the two things can happen quickly:
-
Microsoft tells us that these are automatic requests and close my SkyDrive account and data Remove
-
Microsoft regularly changes authentication front-end, I often need to reprint the portion of my service that interacts with SkyDrive.
Anything else encountered difficulties like this? I would like to hear some feedback on whether it is likely to be worth the effort or not.
What you probably want to do is probably possible, according to technology. But is it allowed under SkyDrive's terms of service? And what is the worst situation if they change their protocol? Would you try to run this business as a business? Have you considered using something like Amazon's simple storage service, which is designed to fix what you want to do? Skydrive Protocol Reverse Engineering Why waste your time?
Comments
Post a Comment