k heitz
asked on
SetHeaderRequest not being sent
Dear Experts -
I'm on the last leg (i hope) of a project I have been struggling with. The Experts here have held my hand thru much of it with success - I am not experienced in this area and have run into another brick wall.
I have a hashed digital signature that needs to be sent to the customers site (which is a proxy). The code below is giving me an http.status response of 12004. I've found very little documentation on this response, except that it can be found as an http error for 'internal error'.
As an aside - he would like me to set the protocol version of my message.
In C# it's done like:
<httpwebrequestobject>.set RequestHea der "Protocol", "System.Net.HttpVersion.Ve rsion10"
I'm not using webrequests; just MSXML2.XMLHTTP. Is there a way to set the protocol w/ this?
And the final issue - the customer is not receiving my
setheaderrequest = "hash", sdigsig.
He has sent me the headers he is receiving (below code)
Here is the code (VB6)
**** code ****
Here is what customer is receiving - i should note he is only receiving intermittent messages.
*** Customer feedback ****
Looking at the log, I d not see this message you just sent, but I do see another one sent about an hour ago.
For that message, the message body says "/Feed". It also is not finding an HTTP Header named "hash". Here are the Headers it is receiving:
http.headers={Accept-Langu age=en-US,
Host=feeds.CUSTOMER.com,
Accept-Encoding=gzip, deflate,
User-Agent=Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.3; .NET4.0C; .NET4.0E),
Keep-Alive=true,
Connection=true,
Accept=*/*}
*** end of customer feedback
Does anyone have ideas what is failing (error 12004) or why he isn't getting my header request "hash" "
Thank you
I'm on the last leg (i hope) of a project I have been struggling with. The Experts here have held my hand thru much of it with success - I am not experienced in this area and have run into another brick wall.
I have a hashed digital signature that needs to be sent to the customers site (which is a proxy). The code below is giving me an http.status response of 12004. I've found very little documentation on this response, except that it can be found as an http error for 'internal error'.
As an aside - he would like me to set the protocol version of my message.
In C# it's done like:
<httpwebrequestobject>.set
I'm not using webrequests; just MSXML2.XMLHTTP. Is there a way to set the protocol w/ this?
And the final issue - the customer is not receiving my
setheaderrequest = "hash", sdigsig.
He has sent me the headers he is receiving (below code)
Here is the code (VB6)
**** code ****
Dim objXML As New MSXML2.XMLHTTP
Set objXmlHttp = CreateObject("MSXML2.XMLHTTP")
'02.20.14 - digital sig to embed in http header...
Dim sDigSig As String
Dim objSig As New DigitalSignature.ComClass1
sDigSig = objSig.GetSignature(strXML)
Set objSig = Nothing
strPost = "https://feeds.CUSTOMER.com/Feed
objXmlHttp.Open "POST", strPost, True
objXmlHttp.setRequestHeader "hash", sDigSig
objXmlHttp.Send (strXML)
**** end codeHere is what customer is receiving - i should note he is only receiving intermittent messages.
*** Customer feedback ****
Looking at the log, I d not see this message you just sent, but I do see another one sent about an hour ago.
For that message, the message body says "/Feed". It also is not finding an HTTP Header named "hash". Here are the Headers it is receiving:
http.headers={Accept-Langu
Host=feeds.CUSTOMER.com,
Accept-Encoding=gzip, deflate,
User-Agent=Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.3; .NET4.0C; .NET4.0E),
Keep-Alive=true,
Connection=true,
Accept=*/*}
*** end of customer feedback
Does anyone have ideas what is failing (error 12004) or why he isn't getting my header request "hash" "
Thank you
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER