D5-D7 ISAPI vs D12.3 ISAPI

[ToddFrankson 10]

So, I am revisiting an ISAPI dll I wrote some time back....

 

I have a bunch of actions.  In particular I have an /index and a /header action.

 

Header generates a header based on input from which action is called and which "options" the end user has selected prior to the call for the action. Simple stuff....

In D5-D7,  this isapi dll could call the header via a get from the Index action (or any other) and everything worked fine (also a footer but we aren't going there yet).

 

Upgrading it to D12.3 

 

If I call the header directly {http://127.0.0.1/script/CC_Web.dll/getheader?cat=6&mob=n) in my browser, it returns the expected header fine

 

Wen called from within an action:

procedure TWebModule1.WebModule1indexAction(Sender: TObject;
  Request: TWebRequest; Response: TWebResponse; var Handled: Boolean);

var

myHeader:String;

Begin

.......

// nmHttp is a visual component TIDHttp;

MyHeader:=nmHttp1.Get('http://127.0.0.1/script/CC_Web.dll/getheader?cat=6&mob='+Mobile);

Response.Content:=MyHeader;

Response.SendResponse;

Handled:=true;

End;

 

My header is blank.  Occasionally I get an Http 1.1 5 error.  Is there something new that ISAPI can not call actions within the same ISAPAI from one action to another?

 

 

If I type this in the browser: http://127.0.0.1/script/CC_Web.dll/getheader?cat=6&mob=n, the header renders perfectly.