NYCPHP Meetup

[Deidra McIntyre]

Don't use a relative path. Hardcode everything with the absolute URL, i.e.
https://... etc.

I know that the way our files are setup; all of the files (secure and
unsecure) are in the same directory. However, to use them for a secure
page, I have to call the files through a secure server using absolute
URLS. If I forget an element and leave it relative, i.e. javascript
include, then I receive those "some items are insecure" messages.

--> Deidra

*******
Red Ibis Hosting
http://www.redibishosting.com

> Dan,
>
> Everything uses a relative path.
>
> Jeff
>
> -----Original Message-----
> From: D C Krook [mailto:dkrook at hotmail.com]
> Sent: Friday, June 06, 2003 9:10 AM
> To: NYPHP Talk
> Subject: Re: [nycphp-talk] Secure/insecure items
>
>
> Jeff,
>
> The most likely cause for this is images, CSS, or JavaScript files that
> are
> referenced absolutely, e.g., hardcoded by using "http://" or in some
> cases
> even "/img/some.gif"
>
> A solution is to use "//img/some.gif" to maintain protocol state
> (https://)
>
>
> -Dan
>
>
>
>>This seems to be an intermittent problem...not sure if it's a code
>> issue, configuration issue, or browser issue (or all of the above??).
>>
>>On the site I'm building, a user clicks on a link which sends them to a
>> secure page. Sometimes a message pops up saying that there are secure
>> and insecure items. I'm not sure what could be causing it? Could it be,
>> perhaps, that there is no cert for the site?
>>
>>Jeff
>>
>
> _________________________________________________________________
> Protect your PC - get McAfee.com VirusScan Online
> http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>
>
>
>
>
>
>
>
>
> --- Unsubscribe at http://nyphp.org/list/ ---