How to soft code stored process drill down URL

[Quentin]

Hi,

When a stored process called via SPWA will generate drill down URL's pointing to other stored processes, I know that instead of hardcoding the server name  and port:

http://your.server:8080/SASStoredProcess/do?

You can soft code it with:

http://&_srvname:&_srvport/SASStoredProcess/do?  

That obviously makes code more portable when you change servers.

That said, is there an easy way to detect whether the session is using http or httpS ?   I still have that part of my URL hard coded, which means when a server changed to https:, I had to update the code.  I would like to soft code the protocol as well as the server name and port.

Thanks,

--Q.

[Vince_SAS]

Can you get by with using the _URL reserved macro variable?

Using Reserved Macro Variables

http://support.sas.com/documentation/cdl/en/stpug/68399/HTML/default/viewer.htm#p184mqqbi9w6qjn1q061...

Vince DelGobbo

SAS R&D

[Quentin]

Thanks @Vince . 

When I looked in _URL, I expected so see something like:

http://your.server:8080/SASStoredProcess/do?

What I actually see is:

/SASStoredProcess/do

Okay, it just hit me.  Is that a relative URL, so no need to the http and server and port is not necessary? 

So I could I could use it as the "root" URL for chaining stored processes?  So tha's what I should have been using all along for chaining stored processes??? sigh.

[Vince_SAS · Accepted solution]

It is "relative" to protocol://server:port

You can find some examples of using _URL here:

Chaining Stored Processes

http://support.sas.com/documentation/cdl/en/stpug/68399/HTML/default/viewer.htm#datapass.htm

For example:

nexturl = "&_URL?_program=/WebApps/MyWebApp/Print Color" || '&fname=' || urlencode("&FNAME");

Vince DelGobbo

SAS R&D

[Quentin]

Thanks Vince. Will file this under things I should have learned years ago. : )