Skip to content

Fixing the TS_HTTP_REQUEST_BUFFER_READ_COMPLETE_HOOK enum value#6243

Closed
bneradt wants to merge 1 commit intoapache:masterfrom
bneradt:fix_request_buffer_read_complete_hook
Closed

Fixing the TS_HTTP_REQUEST_BUFFER_READ_COMPLETE_HOOK enum value#6243
bneradt wants to merge 1 commit intoapache:masterfrom
bneradt:fix_request_buffer_read_complete_hook

Conversation

@bneradt
Copy link
Contributor

@bneradt bneradt commented Dec 4, 2019

The value for TS_HTTP_REQUEST_BUFFER_READ_COMPLETE_HOOK was out of sync with the corresponding event, TS_EVENT_HTTP_REQUEST_BUFFER_READ_COMPLETE. This caused the handler for TS_HTTP_REQUEST_BUFFER_READ_COMPLETE_HOOK to never be invoked with the TS_EVENT_HTTP_REQUEST_BUFFER_READ_COMPLETE event. This patch fixes this problem and adds comments explaining this otherwise implicit but very important requirement that these values correspond as they do.

The naming of the event and hook were off too. A hook with name TS_HTTP_X_HOOK should have an event of name TS_EVENT_HTTP_X, but these got out of sync somehow for request buffer read complete.

@randall randall added this to the 10.0.0 milestone Dec 5, 2019
@bneradt
Copy link
Contributor Author

bneradt commented Dec 5, 2019

[approve ci autest]

2 similar comments
@zizhong
Copy link
Member

zizhong commented Dec 6, 2019

[approve ci autest]

@bneradt
Copy link
Contributor Author

bneradt commented Dec 6, 2019

[approve ci autest]

@bneradt bneradt force-pushed the fix_request_buffer_read_complete_hook branch 2 times, most recently from 6b884d5 to e977c89 Compare December 18, 2019 23:12
@bneradt
Copy link
Contributor Author

bneradt commented Dec 18, 2019

[approve ci autest]

The value for TS_HTTP_REQUEST_BUFFER_READ_COMPLETE_HOOK was out of sync with
the corresponding event, TS_EVENT_HTTP_REQUEST_BUFFER_READ_COMPLETE. This
caused the handler for TS_HTTP_REQUEST_BUFFER_READ_COMPLETE_HOOK to never be
invoked with the TS_EVENT_HTTP_REQUEST_BUFFER_READ_COMPLETE event. This patch
fixes this problem and adds comments explaining the otherwise implicit but
very important requirement that these values correspond as they do.

The naming of the event and hook were off too. A hook with name TS_HTTP_X_HOOK
should have an event of name TS_EVENT_HTTP_X, but these got out of sync somehow
for request buffer read complete. This adjusts the event name appropriately.
@bneradt bneradt force-pushed the fix_request_buffer_read_complete_hook branch from 0c08850 to a911e31 Compare December 19, 2019 17:50
@bneradt
Copy link
Contributor Author

bneradt commented Dec 20, 2019

I'm going to close this PR because I've been getting good review comments for this on the other PR that depends upon this one:

#6259

Since the review work is happening over there for this commit, it's just confusing at this point to have the two PRs.

@bneradt bneradt closed this Dec 20, 2019
@zwoop zwoop removed this from the 10.0.0 milestone Dec 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants