I've read the articles on the RESTDebugger, stepped through the source
& tried to resolve this myself, but I'm stuck here scratching my head.
I'm working on REST trying to take advantage of the DSSESSION to reuse
the existing session that was created during login.  But I can't figure
out how to get this rest debugger to pass through the pragma in a way
that TDSHTTPApplication.GetRequestSessionId will recognize it.

In the debugger params, I have one assigned that looks like this:
[HEADER] Pragma=dssession=32343.221805.242350

In the GetRequestSessionId it recognizes that there is a pragma, but it
can't find it in the stringlist as the values as the
ARequestInfo.Pragma looks like this: 'dssession%3D32343.221805.242350',
where it needs to be
'dssession=32343.221805.242350' for the stringlist to handle it
correctly.

Any suggestions? Thanks



-- 
---
  Rich Werning
  TIP Technologies, Inc.

Richard Werning wrote:

To clarify, you can send it via the URL by using SID or SESSIONID as a
parameter:

http://localhost:8080/Datasnap/rest/TServerMethods1/EchoString?sid=34388
..810447.471204

However I'm trying to figure out how to use it as part of the header
for the json request.

Thanks,
 Rich



> I've read the articles on the RESTDebugger, stepped through the source
> & tried to resolve this myself, but I'm stuck here scratching my head.
> I'm working on REST trying to take advantage of the DSSESSION to reuse
> the existing session that was created during login.  But I can't
> figure out how to get this rest debugger to pass through the pragma
> in a way that TDSHTTPApplication.GetRequestSessionId will recognize
> it.
> 
> In the debugger params, I have one assigned that looks like this:
> [HEADER] Pragma=dssession=32343.221805.242350
> 
> In the GetRequestSessionId it recognizes that there is a pragma, but
> it can't find it in the stringlist as the values as the
> ARequestInfo.Pragma looks like this:
> 'dssession%3D32343.221805.242350', where it needs to be
> 'dssession=32343.221805.242350' for the stringlist to handle it
> correctly.
> 
> Any suggestions? Thanks



-- 
---
  Rich Werning
  TIP Technologies, Inc.