Skip to content

Conversation

@f5yacobucci
Copy link
Contributor

@f5yacobucci f5yacobucci commented Jun 16, 2023

Proposed changes

  • minimal bindings for events (nginx_event_t and company)
  • getters for request status and subrequest depth
  • cycle count increment
  • flags as argument to subrequest
  • subrequest can accept a custom data
  • do not automatically nuke the subrequest body. that should be up to the caller.

avahahn and others added 17 commits June 16, 2023 15:40
Signed-off-by: Ava Hahn <[email protected]>
Signed-off-by: Ava Hahn <[email protected]>
Signed-off-by: Ava Hahn <[email protected]>
- New log macro that accepts NGX_LOG_DEBUG bitmask filters
- Add logging to events
- Updated internal_redirect to call request methods:
  - ngx_named_location, ngx_internal_redirect which accepts args
- Subrequest flags for masking and state
- Subrequest accepts query parameters as the arg flag
- Quelling lint errors and warnings
- Quelling fmt workflow errors
@ivanitskiy
Copy link
Contributor

@f5yacobucci Please remove links to not publicly available repositories.

@f5yacobucci
Copy link
Contributor Author

@f5yacobucci Please remove links to not publicly available repositories.

Can do, can you point me to an example? I'm not seeing one at the moment. Should just be nginx.org dev guide links, but I'll continue to scrub.

/// let ptr = str_to_uchar(pool, data);
/// ```
pub fn str_to_uchar(pool: *mut ngx_pool_t, data: &str) -> *mut u_char {
pub unsafe fn str_to_uchar(pool: *mut ngx_pool_t, data: &str) -> *mut u_char {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is that? when unsafe is used in the body of the fn, it is safe to invoke it, otherwise, the caller must use unsafe to unsafe { str_to_uchar(...) } . it is definitely might break many existing codes, let's keep it back.
what's the reason?

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.

3 participants