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

/__reload route does not use custom headers #60

Open
cboitel opened this issue Feb 5, 2020 · 0 comments
Open

/__reload route does not use custom headers #60

cboitel opened this issue Feb 5, 2020 · 0 comments

Comments

@cboitel
Copy link

cboitel commented Feb 5, 2020

When starting apisprout --header "CustomerHeader: value" uri, apisprout will as expected load the swagger definition at uri provided using the custom header provided. We use it to provide a security access token to access the protected uri resource.

When asking apisprout to reload the definition via a /__reload call:

  • custom header won't be used
  • download will fail (our server reports a 404 if our security heaser isn't sent)
  • apisprout will display 'Reloaded from uri" message and no error is reported
  • apisprout won't fail and will keep on working assuming an empty definition has been provided (all calls to apisprout will result in 404)

Will try to provide a fix via a PR.

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

No branches or pull requests

1 participant