View Complete Thread | FoxWeb Forum Home
Search:
Date:    Msg ID:   
From:    Thread:   
Subject:   
The code was not meant to be used as is.  I included it because it contains the necessary function calls to identify the URL that was requested by the user.  Normally you should only use relative URLs in your scripts, but in cases where you need to switch the URL from HTTP to HTTPS you will need to use some of these functions:
 
<%
* Get base URL path for current folder
UrlString = UrlString + Request.ServerVariables("SERVER_NAME") + ;
    Request.ServerVariables("SCRIPT_NAME")
IF Request.ServerVariables("PATH_INFO") <> Request.ServerVariables("SCRIPT_NAME")
    * For script mapped URLs SCRIPT_NAME is usually the same as PATH_INFO
    UrlString = UrlString + Request.ServerVariables("PATH_INFO")
ENDIF
* Strip the name of the current script from the URL
UrlString = LEFT(UrlString, RAT(UrlString, "/"))
%>
Normal URL in the HTML served by your scripts:
<a href="myscript.fwx">Access MyScript.fwx</a><br>
<br>
Secure Login (force HTTPS):
<a href="https://<%=UrlString%>login.fwx">Access MyScript.fwx</a><br>
 
 

FoxWeb Support Team
support@foxweb.com email

Sent by Joe Goldsmith on 07/18/2006 05:37:49 PM:
Thanks for your kind response. I read through the utility below and ran a short test. I found that it certainly identified the domain correctly but failed to identify HTTPS and the fact that post "443" is open to the web server.
 
Another issue is that I wish to develop the application locally then upload the changes to the co-located web site. Using IIS on WIN XP Pro How do I set up a website to update the application? And, how does the the utility below help me use a local development server please?
 
BTW, the Email notification does not seem to work?
 
Joe
 
 
Sent by FoxWeb Support on 07/17/2006 11:09:53 AM:
Local URLs in your static pages and fwx scripts should never be fully qualified with IP addresses or server names.  This ensures that you do not have to modify your pages whenever you move to a different host name/IP address.
 
Are you using fully qualified URLs because you want to switch from HTTP to HTTPS?  If yes, I recommend that you dynamically construct a self-referencing URL.  The following code should prove useful:
 
DO CASE
CASE Request.ServerVariables("HTTPS") = ""
    * Server does not support HTTPS server variable
    IF Request.ServerVariables("SERVER_PORT") = "443"
        UrlString = "https://"
    ELSE
        UrlString = "http://"
    ENDIF
CASE LOWER(Request.ServerVariables("HTTPS")) = "on"
    UrlString = "https://"
OTHERWISE
    UrlString = "http://"
ENDCASE
UrlString = UrlString + Request.ServerVariables("SERVER_NAME") + ;
    Request.ServerVariables("SCRIPT_NAME")
IF Request.ServerVariables("PATH_INFO") <> Request.ServerVariables("SCRIPT_NAME")
    * For script mapped URLs SCRIPT_NAME is usually the same as PATH_INFO
    UrlString = UrlString + Request.ServerVariables("PATH_INFO")
ENDIF
IF NOT EMPTY(Request.ServerVariables("QUERY_STRING"))
    UrlString = UrlString + "?" + Request.ServerVariables("QUERY_STRING")
ENDIF
 
Another alternative would be to modify your hosts file so as to redirect your hosted site's host name/IP address to your local server.  The problem with this is that this will prevent you from accessing your hosted site from that computer.

FoxWeb Support Team
support@foxweb.com email

Sent by Joe Goldsmith on 07/14/2006 11:21:08 PM:
I have an application that I am just about ready to pack on a new 1U rack mount computer and take to a co-location service. As such, I will need to change IP addresses.
 
The problem is once I send the website to a co-location service how do I not work on the website?
 
Certainly, I can load the website on my local workstation or server but the co-located code has embedded local URLs with HTTPS and other stuff that I cannot test locally as it will want to go over the Internet to the co-located server.
 
Any one have an idea how to maintain, upgrade, and test the website locally?
 
Joe