Website Migration Notice: SafePoint is now operated by CyberServal.Learn more →
DiscussionSLA

Rewrite HTTP Response Header "Server: Tengine"

Published a year ago

# SafeLine WAF

Published a year ago

profile_photo

Linus

Updated 2 years ago

0

Currently the HTTP Header modifications does not support rewriting the "Tengine" Header. When applying a new rule to modify the Response Header "Server" an additional Server header will be added instead of rewriting the existing "Server: Tengine" header.

profile_photo

Linus

Updated 2 years ago

0

Rewrite HTTP Response Header "Server: Tengine"

profile_photo

Monster

Updated 2 years ago

0

I think you meant this
image.png

profile_photo

Linus

Updated 2 years ago

0

Exactly, the module works as expected except for the Header „Server“

profile_photo

Monster

Updated 2 years ago

0

Does Server Header have special logic? Let me verify it.

profile_photo

Naldela Teleyal

Updated 2 years ago

0

I think, that's nginx related. Even if I try to change the Server header directly with nginx, it's unable to rewrite it. At least, when I use nginx as entrypoint.

profile_photo

Linus

Updated a year ago

0

Solution found 🙂

It's possible to passtrough the upstream header by adding proxy_pass_header Server; into each web services advanced config. With this setting the upstream Server header is returned to the client instead of "Server: Tengine".

It would be nice to have this as a global checkbox option for all web services.
image.png

profile_photo

Carrie

Updated a year ago

I'll tell your suggestion to our product and development team.

profile_photo

YaneonY

Updated 9 months ago

0

Anything new on this?

profile_photo

YaneonY

Updated 9 months ago

0

Editing all configs for each page is somehow pain in the ass... 🙁

profile_photo

Carrie

Updated 9 months ago

Is this what you want? You can set up globally in Application -> Advanced -> HTTP Header Settings
image.png

Rewrite HTTP Response Header "Server: Tengine" | CyberServal | CyberServal