Skip to content

Fix for issue #34 - catch HTTP 2XX and return HTTP 200#35

Open
sammcgeown wants to merge 2 commits into
vmw-loginsight:masterfrom
sammcgeown:fix-issue-34---HTTP-200-response-for-log-insight
Open

Fix for issue #34 - catch HTTP 2XX and return HTTP 200#35
sammcgeown wants to merge 2 commits into
vmw-loginsight:masterfrom
sammcgeown:fix-issue-34---HTTP-200-response-for-log-insight

Conversation

@sammcgeown
Copy link
Copy Markdown

Fixes issue #34 where Log Insight expects HTTP 200 and retries the webhook if it doesn't receive it.

Fixes issue vmw-loginsight#34 where Log Insight expects HTTP 200 and retries the webhook if it doesn't receive it.
@vmw-loginsight
Copy link
Copy Markdown
Owner

Hey Sam -- we are considering applying this behavior to the init.py file so that all shims behave the same way (this request on addresses vRO). @alanjcastonguay will be looking next week and can sync with you.

@flands
Copy link
Copy Markdown
Collaborator

flands commented Aug 5, 2017

@alanjcastonguay this is related to the README changes. Are you able to pick this up?

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage decreased (-0.8%) to 75.869% when pulling fa7a228 on sammcgeown:fix-issue-34---HTTP-200-response-for-log-insight into 75b12c0 on vmw-loginsight:master.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants