Change content from text/plain to text/html if swagger service is a sub-element in SICF
#82
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If Swagger service is created as a subelement of a REST service, content type by default comes as `text/plain` and Swagger.html source codes are printed on browser. UI won't be displayed. Parent service request handler needs to be skipped to trigger Swagger service( since it is a child element ). ` me->if_http_extension~lifetime_rc = if_http_extension~co_lifetime_destroy.` ` me->if_http_extension~flow_rc = if_http_extension~co_flow_ok_others_mand`
Co-authored-by: abaplint[bot] <24845621+abaplint[bot]@users.noreply.github.com>
fix for abaplint Co-authored-by: abaplint[bot] <24845621+abaplint[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If Swagger service is created as a subelement of a REST service, content type by default comes as
text/plainand Swagger.html source codes are printed on browser. UI won't be displayed.Parent service request handler needs to be skipped to trigger Swagger service( since it is a child element ) as below.
me->if_http_extension~lifetime_rc = if_http_extension~co_lifetime_destroy.me->if_http_extension~flow_rc = if_http_extension~co_flow_ok_others_mandAbove codes will skip REST handler to be destroyed and child handlers to be triggered. Once Swagger handler is triggered, output can be seen as
text/plainfor content type. This PR will fix it.