Thursday, May 24, 2012

[WD&D] Digest for sitedesign@googlegroups.com - 4 Messages in 2 Topics

Group: http://groups.google.com/group/sitedesign/topics

    Stuart Moules <stu.moules@googlemail.com> May 23 11:12PM +0100  

    I am running WAMP server on Vista Ultimate x64.
     
    I found the php.ini file in this path: C:\wamp\bin\apache\Apache2.2.21\bin
     
    If you installed php with apache you should be able to find it in the
    apache directory somewhere.
     
    Then I opened the start menu on windows, right clicked on notepad and run
    as administrator. Then opened the php.ini file with notepad. Then scroll
    down the php.ini file about half way and you will see allow_url_fopen and
    allow_url_include with an = sign and the word On or Off after them. Just
    delete the word On and type Off for each function you wish to disable, and
    save the notepad or text editor document, not save as. Restart apache, or
    wamp, then test the results with the phpinfo() function and where it stated
    on should now read off.
     

     

    umiwangu <umiwangu@gmail.com> May 23 01:01PM -0700  

    I purchased an SSL certificate last year, but I've been pretty slow in
    implementing it.
     
    Right now, I'm experimenting with forcing certain pages to redirect to the
    secured version, just by using an ASP include. This is working fine.
     
    <%
    If Request.ServerVariables("SERVER_PORT")=80 Then
    Dim strSecureURL
    strSecureURL = "https://"
    strSecureURL = strSecureURL & Request.ServerVariables("SERVER_NAME")
    strSecureURL = strSecureURL & Request.ServerVariables("URL")
    Response.Redirect strSecureURL
    End If
    %>
     
    Now... my only problem is that this then turns all of the links on the page
    into https links, but because not all of the resources on the linked pages
    are secure, the browser will either give a warning, or somehow tell the
    user that the page is not completely secure. Even though it's technically
    not an issue at all, anything that potentially upsets users is bad.
     
    Now, I created another include that forces a page to be delivered across
    the normal HTTP port and without being encrypted. It's basically the same
    as the include above, but switched around.
     
    Does that make sense? If not, I can include a link where you can see it.
     
    So my question is... is this the cleanest way of doing this? I have
    probably over 500 pages on this site, and if I have to do something
    site-wide, I want to do it right.
     
    Thanks in advance!
     
    Seth

     

You received this message because you are subscribed to the Google Group sitedesign.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.

--
You received this because you are subscribed to the "Web Design and Development" group at Google Groups. Messages are prefixed with [WD&D] in the subject. No spam is allowed. Be civil, be professional; try to be helpful & mind your netiquette. All posts are Copyright the original author and the Web Design and Development group. No reproduction of this content is allowed in any electronic or printed form outside the group at Google Groups and the http://www.WDaDg.org website. Any unauthorized use of our copy constitutes illegal Copyright infringement and may well be prosecuted to the full extent of the law. Digital Signature: $©"[W|D|&|D]g"|^|!SiteDesign@GG||#%$
To post to this group, email SiteDesign@googlegroups.com
To unsubscribe, email SiteDesign-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/SiteDesign?hl=en
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)