Skip to content

Conversation

@unguul
Copy link
Contributor

@unguul unguul commented Nov 29, 2018

Added Response header access instructions to the docs.

This should fix #1606 and maybe others.

I suspect the confusion comes from the fact that (most of) everything else offers dot notation access but headers come along with dashes and it breaks.

Copy link
Contributor

@chinesedfan chinesedfan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your PR. But I am afraid that Javascript beginners will still not understand what it means. Can you mention something like the bracket notation and use a real header name?

@unguul
Copy link
Contributor Author

unguul commented Feb 26, 2020

@chinesedfan Thanks for the review. I've added a note about the use of bracket notation. I hope that's better.

I'm tempted to even place a link to the MDN page on HTTP headers. Overkill?

Btw, you might want to bring this PR up to date with master. I did click an update button on this PR page but I don't think it did what I thought it was going to do. I apologize if that broke anything.

Copy link
Contributor

@chinesedfan chinesedfan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@unguul Don't worry. You did the right thing by updating with master. And really appreciate for quick response to such a stale pull request. MDN link can be ignored.

@chinesedfan chinesedfan merged commit 67e560d into axios:master Feb 26, 2020
@unguul unguul deleted the patch-1 branch February 26, 2020 12:44
@axios axios locked and limited conversation to collaborators May 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

get header in GET request with a specific name

2 participants