You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The proxying code for either kafka rest or schema registry needs to proxy not only the request body, but also the request headers. For example, creating schemas via the SR register route only works consistently if the content-type is set to "application/json" (read all the way through to the bottom of the issue).
I suggest that the processors work together to ultimately make a new MultiMap for the proxy request headers through a process not unlike:
Start with copy of the request to-be-proxied headers
Strip out the headers meant only for sidecar to consume (x-cluster-id , x-connection-id)
Add in any new headers needed (like sidecar-managed authorization auth token stuff)
So that efforts made on vscode-side to add in extra headers if / when necessary are honored.
While here, it'd also be AWESOME if there were a quarkus setting we could set when sidecar is launched that would put the proxy code into debugging mode, ala curl -v so that we can see the request URL, headers, and body plus then the response headers + body explicitly logged out.
The text was updated successfully, but these errors were encountered:
The proxying code for either kafka rest or schema registry needs to proxy not only the request body, but also the request headers. For example, creating schemas via the SR register route only works consistently if the content-type is set to "application/json" (read all the way through to the bottom of the issue).
I suggest that the processors work together to ultimately make a new MultiMap for the proxy request headers through a process not unlike:
x-cluster-id
,x-connection-id
)So that efforts made on vscode-side to add in extra headers if / when necessary are honored.
While here, it'd also be AWESOME if there were a quarkus setting we could set when sidecar is launched that would put the proxy code into debugging mode, ala
curl -v
so that we can see the request URL, headers, and body plus then the response headers + body explicitly logged out.The text was updated successfully, but these errors were encountered: