Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TempestaFW blocks GET/HEAD requests with Content-Type or Content-Length headers #2322

Open
2 tasks done
RomanBelozerov opened this issue Jan 13, 2025 · 1 comment · May be fixed by #2341
Open
2 tasks done

TempestaFW blocks GET/HEAD requests with Content-Type or Content-Length headers #2322

RomanBelozerov opened this issue Jan 13, 2025 · 1 comment · May be fixed by #2341
Assignees
Labels
crucial enhancement good to start Start form this tasks if you're new in Tempesta FW
Milestone

Comments

@RomanBelozerov
Copy link
Contributor

RomanBelozerov commented Jan 13, 2025

Scope

I receive Warning in dmesg using TempestaFW as proxy for Jenkins with Blue Ocean plugin:

Warning: Content-Length or Content-Type not allowed to be used with such (overridden) method

A lot of apps can use these headers by default and TemepstaFW will be block them. This can be a problem.

My proposal:

  • remove the check or;
  • add a new directive for disabling the check (global/vhost/location);

Testing

  • add new tests or create a new issue in tempesta-test (probably we need to update DeproxyAutoParser)

Documentation

  • update wiki
@RomanBelozerov RomanBelozerov added enhancement good to start Start form this tasks if you're new in Tempesta FW labels Jan 13, 2025
@RomanBelozerov RomanBelozerov added this to the 0.9 - LA milestone Jan 13, 2025
@krizhanovsky
Copy link
Contributor

Required for S3 compatibility. We need a configuration option to switch on/off this feature

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crucial enhancement good to start Start form this tasks if you're new in Tempesta FW
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants