Why different cURL platforms output different results? Simple cURL POST request

By -

I'm testing something very simple with curl. I've got a PHP server (7.4.30) from a provider which has a page called: form.php. The form.php contains the following code:

<html>
......
  <?php

    echo "Name here::: ";

    if(isset($_POST['submit'])) {
        echo $_POST['name'];
    }

  ?>
......
</html>

All I'm doing is sending post data to this endpoint via:

curl -L http://www.domain.tld/test/form.php -H "Content-Type: application/x-www-form-urlencoded" -d "name=Nde&submit=Submit"

All I'm expecting in the output is to see my name I submitted via curl, but it doesn't. I get: "Name here::: " but nothing else.

 <body>
  Name here:::
 </body>
</html>

When I run the exact same curl command via reqbin.com/curl, it does exactly what I want, showing the name in the html content output.

<body>
    Name here::: Nde
</body>

</html>

I also tried via Git Bash, but it returns the same result as windows curl and I also tried to simulate a POST request via the same server and PHP curl but all seem not to accept my POST data.

I also happen to have another provider and when I do the exact same test on their server, everything works. So it must be something on my provider side, but I have not the faintest idea what the issue could be, given that depending on where I run curl from, it still works.

Does anyone know why I have different results depending on where I run the curl code from?

Thank you



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more