Web service design trade-offs (TCP read mode vs headers)

Question

If I use HTTP headers, I can stimulate and monitor my LV RT code from a web browser while my PC-based LV code is also talking to the LV RT app.  Sometimes, however, the header is the only part that is returned by the web service.  In order to fix this occasional nuisance, the headers can be eliminated so that the Read TCP data in Immediate mode doesn't exit when only the header has been returned.  Unfortunately, the browser interface (in native, non-JavaScript mode) doesn't work any longer so hitting a simple URL request is useless.
Has anyone found a way to get reliable comms with HTTP headers turned on without having to parse the entire return string line-by-line?

Answer 1

Zack.L wrote:
Hi Andy,
Sorry, forgot to post the Source that's use by both AL1.1.4 and AL2.0.1.
Source
begin
insert into scott.json_demo values(:title,:description);
end;
it's failing during the insert?
Yes, it failed during insert using AL2.0.1.
So the above statement produces the following error message:
The symbol "" was ignored.
ORA-06550: line 2, column 74:
PLS-00103: Encountered the symbol "" when expecting one of the following:
begin case declare end exception exit for goto if loop mod
null pragma raise return select update while with
<an identifier> <a double-quoted delimited-idThis suggests to me that an unprintable character (notice how there is nothing between the double quotes - "") has worked its way into your PL/SQL Handler. Note how the error is reported to be a column 74 on line 2, yet line 2 of the above block should only have 58 characters, so at a pure guess somehow there's extra whitespace on line 2, that is confusing the PL/SQL compiler, I suggest re-typing the PL/SQL handler manually and seeing if that cures the problem.