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

fix: use server host and port instead of host header values #1017

Conversation

jjaakola-aiven
Copy link
Contributor

About this change - What it does

References: #xxxxx

Why this way

@jjaakola-aiven jjaakola-aiven requested review from a team as code owners January 7, 2025 11:05
@jjaakola-aiven jjaakola-aiven force-pushed the jjaakola-aiven-fastapi-tracing-cannot-expect-host-header-to-have-port branch 2 times, most recently from 63474c6 to a171574 Compare January 8, 2025 06:45
Copy link

github-actions bot commented Jan 8, 2025

Coverage report

Click to see where and how coverage changed

FileStatementsMissingCoverageCoverage
(new stmts)
Lines missing
  src/karapace
  config.py 33
  src/schema_registry/telemetry
  middleware.py
  tracer.py
Project Total  

This report was generated by python-coverage-comment-action

@jjaakola-aiven jjaakola-aiven force-pushed the jjaakola-aiven-fastapi-tracing-cannot-expect-host-header-to-have-port branch from a171574 to 51b1391 Compare January 9, 2025 07:50
@nosahama nosahama merged commit 2505709 into jjaakola-aiven-fastapi Jan 9, 2025
10 checks passed
@nosahama nosahama deleted the jjaakola-aiven-fastapi-tracing-cannot-expect-host-header-to-have-port branch January 9, 2025 10:57
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.

2 participants