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

How to get HTTP verb? (GET, POST, PUT, HEAD, PATCH) #37

Open
SamuelMarks opened this issue Apr 9, 2014 · 4 comments
Open

How to get HTTP verb? (GET, POST, PUT, HEAD, PATCH) #37

SamuelMarks opened this issue Apr 9, 2014 · 4 comments

Comments

@SamuelMarks
Copy link

The closest I've gotten is the header output (https://github.com/SamuelMarks/node.native/blob/master/routes.h#L54):

$ http localhost:8080/headers
HTTP/1.1 200 OK
Content-Length: 141
Content-Type: application/json

{
    "headers": [
        {
            "Accept": "*/*"
        }, 
        {
            "Accept-Encoding": "gzip, deflate, compress"
        }, 
        {
            "Host": "localhost:8080"
        }, 
        {
            "User-Agent": "HTTPie/0.8.0"
        }
    ]
}

How do I get the HTTP verb?

@sebjameswml
Copy link
Contributor

Hi there.

My fork of node.native adds the ability to get the HTTP body (the body of your POST).

I think you could get the HTTP method by adding code in client_context::parse which will get the method from the http_parser - this has a method attribute which is set in http_parser_execute(). http_parser is one of node.native's submodules.

Cheers,

Seb

@sebjameswml
Copy link
Contributor

Hi Samuel, how did you get on with this one?

@SamuelMarks
Copy link
Author

Didn't get around to it; TBH: I have moved away from C++ now for my web development, namely due to:

  • Segfault when using JSON() in routes.h
  • Linker errors when separating routes.h into routes.h and routes.cc
  • No built-in access to HTTP verbs
  • CMake build not included

@sebjameswml
Copy link
Contributor

Fair enough - you have to do a bit of hacking to use node.native, and that won't appeal to everyone. If you could close this issue, that'd be good.

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

2 participants