#1 2025-05-16 08:27:39

itSDS
Member
From: Germany
Registered: 2014-04-24
Posts: 551

regression in logging

Hi Arnaud,

today i saw that some SOA Parameters i formerly could read are shortened now.
There was a const MAX_SIZE_RESPONSE_LOG which i changed to a larger Value

now this const is not used any more and at the places it was formerly used InternalLogResponse is called!
InterlogResponse uses LogEscape which uses a ShortString now an cuts all after 200 Char.

This is not very useful.

Last edited by itSDS (2025-05-16 08:30:20)


Rad Studio 12.3 Athens

Offline

#2 2025-05-16 08:41:46

itSDS
Member
From: Germany
Registered: 2014-04-24
Posts: 551

Re: regression in logging

As Workaround i changed:

procedure TRest.InternalLogResponse(const aContent: RawByteString;
  const aContext: shortstring; Level: TSynLogLevel);
begin // caller checked that self<>nil and sllServiceReturn in fLogLevel
//  fLogFamily.Add.LogEscape(Level, '%', [aContext], pointer(aContent), length(aContent), self);
  fLogFamily.Add.Log(Level, aContent, self, MAX_SIZE_RESPONSE_LOG);
end;

Rad Studio 12.3 Athens

Offline

Board footer

Powered by FluxBB