Iam setting up a value for http request header in XS 40 box and connecting to XI 52 box. but when I see the XI 52 logs/Probe, I dont see the value populated under Header section. (but I can see the value populated in XS 40 box Header section with name "DPToken")
Code on XS 40 box before sending the request to XI 52box.
<!-- Inserts DPToken header field and its associated value into the HTTP header of a client request. -->
<dp:set-http-request-header name="'DPToken'" value="$SecurityToken"/>
Code return on XI 52 to pull the value present in HttpHeader
<!-- Grab the DPToken from the HTTP header -->
<xsl:variable name="SecurityToken" select="dp:http-request-header('DPToken')"/>
But, I am getting this "SecurityToken" value as NULL. Now I doubt if this dp:http-request-header works good in XI 52 box's?
This topic has been locked.
6 replies Latest Post - 2012-05-01T02:10:57Z by subbu_47
Pinned topic Unable to grab the Http Header values using dp variable in XI 52 box
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-05-01T02:10:57Z at 2012-05-01T02:10:57Z by subbu_47
Re: Unable to grab the Http Header values using dp variable in XI 52 box2012-04-27T16:21:13Z in response to subbu_47The easiest way to investigate this is:
- take a packet capture on either box
- send one request through
- stop packet capture
- open packet capture in Wireshark
- filter for 'tcp.port=abcd' where abcd is your service's port
- do 'Follow TCP stream'
- check whether header gets send or not
Re: Unable to grab the Http Header values using dp variable in XI 52 box2012-04-28T16:30:33Z in response to HermannSWHi Hermann,
Thanks for your reply, I tried to get the packet capture in XS 40 box, but when I try to open the packet capture in wireshark, I am not able to read the data in TCP follow stream, It is not in a readable format even though I selected it as ASCII.
Attached the packet capture for your reference, and I am sending the request from 8089 port(ip address ends with .153) to 444 port(ip address ends with .126).
Pls let me know if anything wrong I did with my packet capture.
Re: Unable to grab the Http Header values using dp variable in XI 52 box2012-04-29T03:14:08Z in response to subbu_47Hi,
please enter "tcp.port==8089" in "Filter:" field of Wireshark and then press enter.
That selects only those packets releated to port 8089.
Right click on any of the (few) packets selected and do "Follow TCP Stream".
This opens a window with your POST and the HTTP response.
The error in "/*/*/*/detail" of the response seems to indicate a problem in your setup (cannot read .dpa).
Re: Unable to grab the Http Header values using dp variable in XI 52 box2012-04-30T20:51:55Z in response to HermannSWHi Harmann,
Thanks alot for your detail explanation, now I have cleared the errors on the dpa part, but now also, I am not getting the value of Header field in my CapturePacket.
But I can see that value in my probe at last mirror(attached probe screen shot for your reference).
But in wireShark, I can only these below values but not my "DpToken" which I set up in my httpHeader using xslcode.
============================ wireShark TcpFollowStream at tcp.port == 8089
POST /BenefitsService/1.0/GetEOCSummary HTTP/1.1
User-Agent: Jakarta Commons-HttpClient/3.1
Via: 1.1 AAAAAH0KAAA-,1.1 AAAAAIMKAAA-
Pls let me know if anything is any other ways to findout.
Re: Unable to grab the Http Header values using dp variable in XI 52 box2012-04-30T23:02:12Z in response to subbu_47Hi,
that is good news in that you now have proven two things:
- DPToken header is set in last context before result action
- DPToken header is not set in request posted
Please create a PMR to narrow down the issue, and identify whether this is a bug or configuration issue.
Level2 support will collect the required data from you needed for investigation (config, requests, ...).