Wrox Home  
Search P2P Archive for: Go

  Return to Index  

asp_web_howto thread: Secure included code


Message #1 by scottd@c... on Wed, 11 Sep 2002 18:54:53
Hi Everyone,

Okay - let's say you want to add a few monthly-billable service-related 
features to client's website via an include. How would you protect your 
code in the event the client quits the service?

I'm picturing the include residing in MY domain, and tossing in a little 
DB lookup to verify the clients account is current before coughing up the 
code, but is this the best way? Any thoughts on protecting the code built 
into the website (JavaScript and asp elements) not specifically 'included'.

And can a virtual include use a FQDN? <!-- #include 
virtual="www.blahblahblah.com/ASP_inclues/yowza.asp" -->?

Please advise and TIA
Message #2 by "Ken Schaefer" <ken@a...> on Thu, 12 Sep 2002 12:14:26 +1000
Includes require physical path.

Think about it: you want the ASP inside the include to be executed on the
webserver right? So the ASP source code needs to be available to the
webserver. But, if I can use a FQDN to get an ASP include file (including
the source code), then I can pinch anyone's ASP page from anywhere on the
'net!

What are your options:
a) Create a component, ie a .dll
b) Use a webservice + SOAP (this is probably better), since it's easy to
"disconnect" the client when/if they decide to go a different way...
c) Along similar lines, you could have code on the ASP page that uses the MS
XMLHTTP component to do a GET/POST to your server, and retrieve a result.

Cheers
Ken

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From: <scottd@c...>
Subject: [asp_web_howto] Secure included code


: Hi Everyone,
:
: Okay - let's say you want to add a few monthly-billable service-related
: features to client's website via an include. How would you protect your
: code in the event the client quits the service?
:
: I'm picturing the include residing in MY domain, and tossing in a little
: DB lookup to verify the clients account is current before coughing up the
: code, but is this the best way? Any thoughts on protecting the code built
: into the website (JavaScript and asp elements) not specifically
'included'.
:
: And can a virtual include use a FQDN? <!-- #include
: virtual="www.blahblahblah.com/ASP_inclues/yowza.asp" -->?
:
: Please advise and TIA
:
: ---
:
: Improve your web design skills with these new books from Glasshaus.
:
: Usable Web Menus
: http://www.amazon.com/exec/obidos/ASIN/1904151027/ref=nosim/theprogramme
: r-20
: Constructing Accessible Web Sites
: http://www.amazon.com/exec/obidos/ASIN/1904151000/ref=nosim/theprogramme
: r-20
: Practical JavaScript for the Usable Web
: http://www.amazon.com/exec/obidos/ASIN/1904151051/ref=nosim/theprogramme
: r-20


  Return to Index