I'm curious if anyone has an experience in protecting
a web-based interface from being "front-ended" by others
for their own gain.
Say I spent a good amount of time and money to develop
a site that sells "ProductX". Someone then reverse engineers my HTML form->submit process and creates their
own front-end, secretly adding an upcharge to the customer.
They also change all references to ProductX to ProductY,
so I may not be able to manually search for and identify
who's screen scraping.
What I've thought of:
- Dynamically changing form element names, perhaps tied
to a Digest::MD5 hash of the session key. Might help, but
they could still guess some of that based on the provided
values of the form elements.
- Having the user type in text that matches what's
displayed in a .gif image. ( See This pretty cool node from jcwren on defeating this sort of thing ).
This bothers me, because I'm making the customer jump through hoops to buy something
- Analyze web logs to find those people taking an
odd path through the site. ( skipping intro pages ).
Turns out this isn't useful, since there so much client-side caching.
Any other ideas ? Any modules that might help me ?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|