-
Notifications
You must be signed in to change notification settings - Fork 2.5k
[Http] Add body support for DELETE/OPTIONS request #6492
Conversation
Seems related to #6318, which will land only in 2.4. Could you eventually add a test, especially for |
@Ocramius Should I add some tests which will be specific to curl or shared by all adapters? |
@egeloen whatever makes more sense for you |
@weierophinney have we ever tried enabling the HTTP integration tests on travis? |
I can enable it on travis but which web server should I use? nginx, apache, an other? |
We can use the internal PHP Server Marco Pivetta On 30 July 2014 16:38, Eric GELOEN notifications@github.com wrote:
|
I just try to use the PHP built in web server and there is lot of tests which fails (more than with a real web server). So, I'm not sure it's a good idea to rely on it. |
I'm not sure if travis comes with any pre-installed web server, because I don't think we should install one during builds either. Yes, the internal PHP server is indeed very simplified: I was hoping for it to support our necessities :\ |
Unfortunately, travis does not come with a web server as pointed here. We need to install/configure it during the build. So, if you think it's a no go to install it, I can't do anything :s |
Re-assigning to @weierophinney - I'll let this decision to him. The question here is build times, mainly. |
@weierophinney Can you please give me your opinion? |
@Ocramius Thank you too! |
…, removed duplicate/redundant `elseif` statements
…e boolean expression
…post-request-body' Close zendframework/zendframework#6492
…post-request-body' into develop Close zendframework/zendframework#6492 Forward port zendframework/zendframework#6492
…l HTTP Client adapter
Hey!
This PR adds support for request body with other methods such as DELETE/OPTIONS with the curl client. Currently, it is only supported with the socket client and so, this PR rationalized the behavior between all clients.