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

Add the http.block_service_list property #1298

Closed
YasasRangika opened this issue Jan 23, 2023 · 2 comments · May be fixed by wso2/product-apim#13097
Closed

Add the http.block_service_list property #1298

YasasRangika opened this issue Jan 23, 2023 · 2 comments · May be fixed by wso2/product-apim#13097

Comments

@YasasRangika
Copy link

Description

I’ve have tested in the API Manager 4.1.0 update 50 adding the following configuration in the deployment.toml
[transport.http]
block_service_list = false
But it seems to have no effect. I can confirm that the feature is added since the code is available [1] and I tested adding http.block_service_list=true in passthru-http.properties.j2 file and worked as expected.
I could confirm that some mappings are missing comparing the configurations of the api manager directory with the EI 7.1.0 (where the feature was added [2] [3])

Please do the necessary for supporting the property in the deployment.toml file

[1] https://github.com/wso2-support/wso2-synapse/blob/69a1633fd0d6453bd150730b2ad123e76c5bf539/modules/transports/core/nhttp/src/main/java/org/apache/synapse/transport/passthru/config/PassThroughConfiguration.java#L163
[2] https://support-internal.wso2.com/jira/browse/EIINTERNAL-1452
[3] wso2/micro-integrator#2548

Steps to Reproduce

N/A

Affected Component

APIM

Version

4.1.0

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

No response

Suggested Labels

No response

@YasasRangika
Copy link
Author

This should close after merging wso2/product-apim#13097. The PR is waiting to merge due to wso2/product-apim#13097 (comment).

@YasasRangika
Copy link
Author

closing this issue since the above issue is tracked as an internal issue.

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

Successfully merging a pull request may close this issue.

1 participant