[jira] [Resolved] (CAMEL-15287) Non-uniform way to handle nulls in http clients

["Claus Ibsen (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-15287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-15287.
---------------------------------
    Resolution: Won't Fix

> Non-uniform way to handle nulls in http clients
> -----------------------------------------------
>
>                 Key: CAMEL-15287
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15287
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: Nicola Ferraro
>            Priority: Major
>             Fix For: 3.x
>
>
> Suppose you have an external Quarkus service that replies always with null.
>  
> When calling it from a camel route via:
> {code:java}
> .to("http://quarkus-service/null-api") {code}
> Then the body of the exchange is null.
>  
> But if we use:
>  
> {code:java}
>  .to("netty-http:http://quarkus-service/null-api"){code}
>  
> Then the body becomes an empty InputStream, which is not null.
>  
> I don't know what's the correct way to handle such cases, but we should try to uniform them.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)