webuipoc: Integrate request-response API

[MZ-AD]

WIP issue zaproxy/zaproxy#8287

[thc202]

The branch has conflicts.

[thc202]

The request/response header fields should be shown each on its own line (like in the desktop).

[MZ-AD]

The request/response header fields should be shown each on its own line (like in the desktop).

Are you talking about this kind of separator, (Separated Head n Body)

[thc202]

No, I mean each header field is in its own line (host: … in one line, User-Agent: … other line and so on). Compare to:

which have the host and user-agent in the same line (along the others).

[thc202]

Both the request and response header fields should be handled the same way.

[thc202]

They should also be aligned to the start of the line. And the bodies should keep their original indentation.

[MZ-AD]

[njmulsqb]

We won't split request/response body on the basis of new line ('\n')

[thc202]

And the bodies should keep their original indentation.

This was not yet addressed.

[thc202]

It would be better if it didn't show the response when it's empty (i.e. HTTP/1.0 0 )

[psiinon]

Checkmarx One – Scan Summary & Details – e7c661d4-5386-48a9-bccf-75831b2185f0

Fixed Issues (1)

Great job! The following issues were fixed in this Pull Request

Severity	Issue	Source File / Package
	Heap_Inspection	/addOns/authhelper/src/main/java/org/zaproxy/addon/authhelper/AuthUtils.java: 401

[MZ-AD]

It would be better if it didn't show the response when it's empty (i.e. HTTP/1.0 0 )

Its fixed now, kindly have a look 9ed9a5a