You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@servicecomb.apache.org by "YaoHaishi (JIRA)" <ji...@apache.org> on 2019/06/02 10:17:00 UTC

[jira] [Comment Edited] (SCB-1278) ServiceComb related headers are not exposed to 3rd party services by default

    [ https://issues.apache.org/jira/browse/SCB-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841868#comment-16841868 ] 

YaoHaishi edited comment on SCB-1278 at 6/2/19 10:16 AM:
---------------------------------------------------------

The specific solution is that:
 1. add a property in org.apache.servicecomb.serviceregistry.api.registry.Microservice to check whether it is a 3rd party microservice.
 2. filter out x-cse* headers added by ServiceComb-Java-Chassis in 3rd party client requests by default. And add a config item to allow users to disable this feature.


was (Author: yaohaishi):
The specific solution is that:
 1. add a property in org.apache.servicecomb.serviceregistry.api.registry.MicroserviceInstance to check whether a certain invocation is a 3rd party invocation.
 2. filter out x-cse* headers in 3rd party client requests by default. And add a config item to allow users to disable this feature.
 3. Add a regex config to allow users specify which kind of request headers should be filtered out in 3rd party invocations

> ServiceComb related headers are not exposed to 3rd party services by default
> ----------------------------------------------------------------------------
>
>                 Key: SCB-1278
>                 URL: https://issues.apache.org/jira/browse/SCB-1278
>             Project: Apache ServiceComb
>          Issue Type: Improvement
>            Reporter: YaoHaishi
>            Assignee: YaoHaishi
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, ServiceComb headers such as x-cse-target-microservice, x-cse-context are sent to 3rd party services and users cannot stop this behavior.
> This behavior should be disabled by default. And a certain way should be provided to let users enable it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)