Errors in Http-session termination

[KBazX 0]

ICS V9.3

I execute a test http-request with the MaxBodySize property with a value that is obviously less than the response size.

I noticed the following errors:
- Events OnRestRequestDone and OnRequestDone are executed twice.
- In repeating events, the property ReasonPhrase has a repeating status code.
 

................
................
................

HttpRest - DocEnd

HttpRest - RestRequestDone
        RqType: GET
        ErrCode: 3
        Error:
            RequestDoneErrorStr: Aborted
            StatusCode: 404
            ReasonPhrase: "404 Aborting connection, Body Size too Large: 369"

HttpRest - RequestDone
        RqType: GET
        ErrCode: 3
        Error:
            RequestDoneErrorStr: Aborted
            StatusCode: 404
            ReasonPhrase: "404 Aborting connection, Body Size too Large: 369"

HttpRest - RestRequestDone
        RqType: GET
        ErrCode: 3
        Error:
            RequestDoneErrorStr: Aborted
            StatusCode: 404
            ReasonPhrase: "404 404 Aborting connection, Body Size too Large: 369"

HttpRest - RequestDone
        RqType: GET
        ErrCode: 3
        Error:
            RequestDoneErrorStr: Aborted
            StatusCode: 404
            ReasonPhrase: "404 404 Aborting connection, Body Size too Large: 369"

 

[Angus Robertson 574]

There are several ways to use the HttpRest component, it is possible events may sometimes be called more than once.  Is it a problem?

 

Angus

 

[KBazX 0]

3 minutes ago, Angus Robertson said:

There are several ways to use the HttpRest component, it is possible events may sometimes be called more than once.  Is it a problem?

No. But there may be a bug.

[FPiette 381]

28 minutes ago, Angus Robertson said:

There are several ways to use the HttpRest component, it is possible events may sometimes be called more than once.  Is it a problem?

It is a problem for application which make use of a state machine, something I use frequently. Having an event triggered twice add useless complexity at the application level and leads to bugs, especially for "final" event like OnRequestDone. It is better to handle that in the component.