Don't think so.
Is that URL you're checking on the internet?  If so I can test it and tell
you exactly what comes back.  


Dirk.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of RAISKIN,HOLLY (HP-Boise,ex1)
Sent: Tuesday, January 13, 2004 6:50 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [SA-list]URL Additional Headers

The entire server requires HTTPS.  We have always had this configuration and
the checks worked until the authentication methods were updated recently by
adding SiteMinder framework in between the destination server and the
clients.  

SiteMinder requests more information and apparently passes more information
back.  Is it possible that there is a limit on the information that
ServersAlive can receive back from the server?

Thanks,
Holly

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Dirk Bulinckx
Sent: Monday, January 12, 2004 8:48 AM
To: [EMAIL PROTECTED]
Subject: RE: [SA-list]URL Additional Headers

Do you see the same issue when using HTTP?

(problem is that an HTTPS can be traced, however the trace is not realy
readable) 


Dirk.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of RAISKIN,HOLLY (HP-Boise,ex1)
Sent: Monday, January 12, 2004 5:06 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [SA-list]URL Additional Headers

The SA documentation did not indicate what the default headers were being
passed.  The destination server logs were denying access to the SA client
with errors that the header:HOST was not received.  Adding the
additionalheaders parameter resolved the issue, according to destination
server logs.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Dirk Bulinckx
Sent: Friday, January 09, 2004 11:28 PM
To: [EMAIL PROTECTED]
Subject: RE: [SA-list]URL Additional Headers

My first question would be why do you need the HOST header?  If I remember
correctly that's something that is automaticly added already to all
requests. 


Dirk.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of RAISKIN,HOLLY (HP-Boise,ex1)
Sent: Saturday, January 10, 2004 2:25 AM
To: '[EMAIL PROTECTED]'
Subject: [SA-list]URL Additional Headers

Hello,

I have been doing a URL check to a secure server using a certificate merged
into IE for several months.  Recently a change in method of login has
required me to pass another variable to connect to the URL, so I added
#ADDITIONALHEADERS=HOST: hostname.xyz.com#"  (the urls/hostnames are not
actuals)

I added the ADDITIONALHEADERS based on documentation from pg 135, 15Feb2003
documentation.  Based on the target server logs, I am now passing the HOST
variable correctly, but there is now a SA error and it basically halts the
remainder of the checking until this check returns, in this case 1616284 ms
later.  Before adding this parameter the check returned a response in about
20000 ms.  Here is the error from the SA Logs: 
************
Friday, January 09, 2004 6:01:31 PM URL check
(https://hostname.xyz.com/check.nsf/home) failed due to [10049] Can't assign
requested address(line  0)
Friday, January 09, 2004 6:01:31 PM URL check took  1616284 ms
************

Does anyone either know where to start looking to correct the 10049 error or
if I have made a syntax error in the adding of the Add'l Headers parameter?


Any assistance is appreciated.

Thanks,

Holly Raiskin



Configuration File entry for reference:
-------------------------------------------------------------------
#NAM=192.168.1.1#PRT="XYZ"#HID=311#DEP=228#DPS=5#GRP=G00000000#REM=""#UID=23
0#ACT=T#VIA="#DE=__LAN__#KA=F#"#LDEFUP=1/9/2004 4:20:28 PM#
#TYPE=U#PARA="#URL=https://hostname.xyz.com/check.nsf/home#CCO=CON#CON=what'
s
new#AUTH=F#USR=#PWD=#PRX=F#COO=F#CRS=F#"#ADPA="#SSLCERTSTORE=MY#SSLCERTSUBJE
CT=O=xyz.com, OU=Servers, O=XYZ,
CN=ADTMonitorBadge.xyz.com#"#ADDITIONALHEADERS=HOST:
hostname.xyz.com#"#TIME=120#SK=T#
#ALERTS=1#WHAT0="#WHAT=SMTPP#TO=(PID= 4),[EMAIL PROTECTED]
is %s: %t : %h + %c : SAlive#MSG=#"#WHEN0=2_DOWN_BACKUP#VIA0="#
#HTML=1,2,#SLOG="#SYSLOG=F#FAC=0#MSG=%h is %s#"#
#MON=555555555555555555555555555555555555555555555555#TUE=555555555555555555
555555555555555555555555555555#WED=55555555555555555555555555555555555555555
5555555#THU=555555555555555555555555555555555555555555555555#FRI=55555555555
5555555555555555555555555555555555555#SAT=5555555555555555555555555555555555
55555555555555#SUN=555555555555555555555555555555555555555555555555#PRI=1#IW
D=F#    #STATUS=6#NRD=0#TLSC=#DLSC=#TLC=#DLC=#
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
   unsubscribe SAlive



To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
   unsubscribe SAlive
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
   unsubscribe SAlive



To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
   unsubscribe SAlive
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
   unsubscribe SAlive



To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
   unsubscribe SAlive

Reply via email to