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.

Sign up for GitHub

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

Jump to bottom

(3.2+) consider setting a more specific HTTP Server header #378

Closed
spoonincode opened this issue Oct 25, 2022 · 0 comments · Fixed by #439
Closed

(3.2+) consider setting a more specific HTTP Server header #378

spoonincode opened this issue Oct 25, 2022 · 0 comments · Fixed by #439
Labels
discussion enhancement New feature or request

Comments

@spoonincode
Copy link
Member

After the beast migration, the HTTP headers in the response includes Server: Boost.Beast/330 (or possibly some other number based on boost version being used). This isn't any weirder than pre 3.2, which has Server: WebSocket++/0.7.0, but maybe we can consider modifying this to nodeos/3.2.0 or something.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion enhancement New feature or request
Projects
Team Backlog
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[3.2 -> main] change the HTTP Server header to be nodeos/keosd version AntelopeIO/leap
3 participants
@heifner @spoonincode @enf-ci-bot