Commitd4ccaec

committed

Merge pull request#386 from ax3l/master

More thorough documentation of 403 response when User-Agent header is invalid.

2 parentsa6cdfa9 +0d5c2ca commitd4ccaecCopy full SHA for d4ccaec

File tree

+13

-0

lines changed

+13

-0

lines changed

Lines changed: 13 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -386,6 +386,19 @@ Here's an example:`
`386`	`386`	`User-Agent: Awesome-Octocat-App`
`387`	`387`	`</pre>`
`388`	`388`
	`389`	+If you provide an invalid`User-Agent` header, you will receive a`403 Forbidden` response:
	`390`	`+`
	`391`	`+<preclass="terminal">`
	`392`	`+curl -iH 'User-Agent: ' https://api.github.com/meta`
	`393`	`+HTTP/1.0 403 Forbidden`
	`394`	`+Connection: close`
	`395`	`+Content-Type: text/html`
	`396`	`+`
	`397`	`+Request forbidden by administrative rules.`
	`398`	`+Please make sure your request has a User-Agent header.`
	`399`	`+Check https://developer.github.com for other possible causes.`
	`400`	`+</pre>`
	`401`	`+`
`389`	`402`	`##Conditional requests`
`390`	`403`
`391`	`404`	Most responses return an`ETag` header. Many responses also return a`Last-Modified` header. You can use the values

Comments

(0)