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

Additional Content-Type header present in the response #8854

Closed
akila95fernando opened this issue Jul 30, 2020 · 1 comment
Closed

Additional Content-Type header present in the response #8854

akila95fernando opened this issue Jul 30, 2020 · 1 comment

Comments

@akila95fernando
Copy link

Description:

When invoking a backend that sends content-type (simple case) header through API manager, Client receives the response with 2 content-type headers ( content-type and Content-Type ) .

[2020-07-28 19:57:58,130] DEBUG - wire HTTP-Listener I/O dispatcher-5 << "Access-Control-Allow-Methods: DELETE,POST,PATCH,PUT,GET[\r][\n]"

[2020-07-28 19:57:58,130] DEBUG - wire HTTP-Listener I/O dispatcher-5 << "content-type: application/xml[\r][\n]"

[2020-07-28 19:57:58,130] DEBUG - wire HTTP-Listener I/O dispatcher-5 << "Access-Control-Allow-Headers: authorization,Access-Control-Allow-Origin,Content-Type,SOAPAction[\r][\n]"

[2020-07-28 19:57:58,130] DEBUG - wire HTTP-Listener I/O dispatcher-5 << "Content-Type: application/xml; charset=UTF-8[\r][\n]"

[2020-07-28 19:57:58,130] DEBUG - wire HTTP-Listener I/O dispatcher-5 << "Date: Tue, 28 Jul 2020 14:27:58 GMT[\r][\n]"

[2020-07-28 19:57:58,130] DEBUG - wire HTTP-Listener I/O dispatcher-5 << "Transfer-Encoding: chunked[\r][\n]"

[2020-07-28 19:57:58,130] DEBUG - wire HTTP-Listener I/O dispatcher-5 << "Connection: keep-alive[\r][\n]"

[2020-07-28 19:57:58,130] DEBUG - wire HTTP-Listener I/O dispatcher-5 << "[\r][\n]"

[2020-07-28 19:57:58,130] DEBUG - wire HTTP-Listener I/O dispatcher-5 << "2e[\r][\n]"

[2020-07-28 19:57:58,130] DEBUG - wire HTTP-Listener I/O dispatcher-5 << "<html><head><title>Error</title></head></html>[\r][\n]"

Steps to reproduce:

  1. Create backend that sends content-type header with the response
  2. Create a new REST API with defined backend Endpoint in publisher
  3. Add a log full mediator to the mediation outflow
  4. Enable wire logs
  5. Invoke the API

Affected Product Version:

APIM-2.2.0

@vithu30
Copy link
Contributor

vithu30 commented Sep 8, 2020

Fixed in master with PR - wso2/wso2-synapse#1622

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants