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

[raw] Include HTTP method and path #23

Merged
merged 2 commits into from Oct 12, 2014
Merged

[raw] Include HTTP method and path #23

merged 2 commits into from Oct 12, 2014

Conversation

kylef
Copy link
Member

@kylef kylef commented Oct 7, 2014

No description provided.

@abtris
Copy link
Contributor

abtris commented Oct 7, 2014

image

In V1 look good. In V3 we have information about method and URL in machine column yes.

@@ -1,6 +1,7 @@
<section name="raw" class="raw">
<p class="ioDesc">Request</p>
<pre class="incoming"><code><% for header, value of @headers: %>
<pre class="incoming"><code><%= @method.toUpperCase() %> <%= @url %> HTTP/1.0
Copy link
Member

Choose a reason for hiding this comment

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

I'd go for HTTP/1.1, because there might be headers, and OPTIONS method (especially this one is important for CORS support) that are not supported by HTTP/1.0. See http://stackoverflow.com/questions/246859/http-1-0-vs-1-1

Copy link
Member Author

Choose a reason for hiding this comment

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

Ah yes, I considered 1.1 but chosen 1.0 so we don't have to deal with persistent HTTP connection's. Will change to 1.1 (for CORS/OPTIONS etc).

abtris added a commit that referenced this pull request Oct 12, 2014
[raw] Include HTTP method and path
@abtris abtris merged commit 8522784 into apiaryio:master Oct 12, 2014
@kylef kylef deleted the raw branch October 12, 2014 22:32
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

3 participants