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

Fix for #71: Show response message on 400, 401 and 404. #72

Merged
merged 7 commits into from
May 5, 2015
Merged

Fix for #71: Show response message on 400, 401 and 404. #72

merged 7 commits into from
May 5, 2015

Conversation

CupOfTea696
Copy link
Contributor

Adds the actual response message to the errors thrown on 400, 401 and
404 response codes. This provides a lot more useful info than the
current messages. The message doesn’t really give you much to go on. I
spent hours trying to find what I did wrong, double checking my API
keys and looking up the error on google.

Adds the actual response message to the errors thrown on 400, 401 and
404 response codes. This provides a lot more useful info than the
current messages. The message doesn’t really give you much to go one. I
spent hours trying to find what I did wrong, double checking my API
keys and looking up the error on google.
@CupOfTea696
Copy link
Contributor Author

Fix for #49, #67 and #71
Fix for Bogardo/Mailgun #39

@CupOfTea696
Copy link
Contributor Author

You can blame @Bogardo for that last commit.

@Bogardo
Copy link

Bogardo commented Jan 13, 2015

I take full responsibility ;)

@Bogardo
Copy link

Bogardo commented Mar 22, 2015

@travelton What is the status on this?

@jessespears
Copy link
Contributor

Sorry all, @travelton isn't on this project anymore, but I am. Sorry for the delay, let me test this out!

@Bogardo
Copy link

Bogardo commented Apr 6, 2015

@jessespears Any news on this?

jessespears pushed a commit that referenced this pull request May 5, 2015
Fix for #71: Show response message on 400, 401 and 404.
@jessespears jessespears merged commit c0ec731 into mailgun:master May 5, 2015
@jessespears
Copy link
Contributor

Thanks for the PR, and sorry for the delay!

@CupOfTea696
Copy link
Contributor Author

No problem, and most welcome!

@yalmaa
Copy link

yalmaa commented Feb 10, 2016

Hello,_ how are you?

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.

None yet

4 participants