[nycphp-talk] Secure/insecure items
Jeff
jsiegel1 at optonline.net
Fri Jun 6 15:15:05 EDT 2003
I'd love to be able to do it but...at this stage it ain't that easy.
Because the website needed to be "update-able" by the client (who uses
DreamWeaver) I had to work with the DreamWeaver template concept.
However, since there are about 80 search-engine optimized pages that all
required fixed paths, etc., adding one additional page to their task
list of pages to update (in the event of a template change) probably
won't kill them.
Jeff
-----Original Message-----
From: Emmanuel. M. Decarie [mailto:emm at scriptdigital.com]
Sent: Friday, June 06, 2003 1:26 PM
To: NYPHP Talk
Subject: RE: [nycphp-talk] Secure/insecure items
Jeff,
Can you call these files dynamically and tell PHP to add 'http://' or
'https://' when required?
This what I have done in another project (not a PHP project) a while
ago and it was working well for me. In the session, I had set a value
telling me if I was on a secure page, and then switched from:
http://www.myserver.com/style.css
to:
https://www.myserver.com/style.css
HTH
Cheers
-Emmanuel
>The only "issue" I have with that is that the page in question is part
>of a set of DreamWeaver templates so...if my client decides to change
>the template then this particular page would have to be changed by
hand.
>However, if this is the only way to eliminate the problem...so be it.
>
>Thank you and everyone for your speedy replies.
>
>Jeff
--
______________________________________________________________________
Emmanuel Décarie / Programmation pour le Web - Programming for the Web
Radio UserLand/Frontier - Perl - PHP - Javascript
<http://scriptdigital.com/>
Blog: <http://blog.scriptdigital.com> - AIM: scriptdigital
--- Unsubscribe at http://nyphp.org/list/ ---
More information about the talk
mailing list