for-get / know-your-http-well Goto Github PK

Many of the links in the Status entry are to protected tweets, and therefore inaccessible to the general viewing public

The docset does not have an index page set. See http://kapeli.com/docsets#settingindexpage for details on how to add this.

https://w3c.github.io/server-timing/

https://github.com/igrigorik/http-client-hints
https://github.com/mnot/I-D/tree/master/http-key

The Cookie spec that documents what tools (browsers, etc.) actually implement is RFC 6265

readme is out-of-sync with emacs modules

https://tools.ietf.org/html/rfc7538

http://tools.ietf.org/html/draft-alakuijala-brotli

https://github.com/inadarei/draft-prefer-transclude

CORS http://www.w3.org/TR/cors/ is not in there right now, correct? that might be a good thing to add, right?

https://tools.ietf.org/html/draft-thomson-http-encryption

"507 Insufficient Storage" links to rfc2518.html#section-10.7. Unfortunately #section-10.7 does not exist in the rfc2518.html page.

CONNECT is not Safe: https://tools.ietf.org/html/rfc7231#section-8.1.3

I am using raml-js-parser-2 which uses raml-definition-system which uses this module as dependency and during webpacking i am getting an error Error: define cannot be used indirect. Debugging error i found out that this module uses amdefine and my error is on that.

Looking into source code, I changed js/index.js file to use global function instead amdefine and it worked fine after webpacking.

Can anything be done about amdefine with webpack?

We got 0.3.0 last month in 13858ba, but it'd be great to have a tagged release for MELPA.

Thanks!

the tweet said

HTTP response codes for dummies. 50x: we fucked up. 40x: you fucked up. 30x: ask that dude over there. 20x: cool.

closed, wrong

https://tools.ietf.org/html/rfc6839

Hi,

Just installed your package and noticed that you don't use completing-read. Any reason why?

I can submit a pull request with the changes, but the source indicates that it was auto generated and I don't see where this is done.

Possibly related to #1

Sometimes you have no idea how a relation/status-code/header/etc is named,
so it's better to just open up a buffer with the the .el/.md file.

(defun http-list-status-codes ...)
...

npm only has version 0.2.0. Could you publish the latest version to npm, @andreineculau?

The RFC might be a joke but it's typically supported by most libraries pertaining to HTTP.

being an XML dinosaur, i'd love to get all of this as XML. but then again, there probably is not a enough regularity in the current markdown, so maybe that's too much to ask for? in whichever way it's implemented, wouldn't it be great to have a machine-readable version of all of this information? it would be simple to generate markdown, but much simpler to also generate other formats: whatever people want. and out of curiosity: how are the emacs and js versions generated currently?

https://github.com/nate-parrott/Flashlight/wiki/Creating-a-Plugin

as alternative to #35 #31

I found one entry that points to a page that does not exist: 7xx Developer Error. Note: there might be other pages that don't exist (I haven't checked all).

When adding https://raw.githubusercontent.com/for-GET/know-your-http-well/master/docset/know-your-http-well.xml to Zeal it just shows a dialog saying Could not read docset feed!

I saw the methods.json, i tried to find POST method and found it wa missing.

Kindly add it.

and nice work.

https://tools.ietf.org/html/draft-ietf-httpbis-early-hints-05

Docset does not have an icon. See http://kapeli.com/docsets#addingicon for instructions on how to add this.

I've set up a repo where users can contribute docsets to Dash. You can check it out at https://github.com/Kapeli/Dash-User-Contributions. It should contain all the info you need to get started.

Docsets that are contributed in this way will appear in a separate User Contributed section under Dash's Preferences > Downloads (i.e. just like the current Ruby Gems or Cocoa Pods sections).

If you need any help with this, don't hesitate to contact me. Thank you!

status-codes.md mentions RFC5218 several times. This is a typo for 2518.

RFC 2518 is obsoleted by RFC 4918.

Have you tried the following?

https://github.com/Kapeli/Dash-User-Contributions#contribute-a-new-docset

It seems to be the recent process for user-contributed doc-sets.