# 5.0.0-alpha5: XPUT Mapping response: "curl: (52) Empty reply from server"

**URL:** https://discuss.elastic.co/t/5-0-0-alpha5-xput-mapping-response-curl-52-empty-reply-from-server/64869
**Category:** Elasticsearch
**Created:** [November 3, 2016, 1:27pm UTC](https://discuss.elastic.co/t/5-0-0-alpha5-xput-mapping-response-curl-52-empty-reply-from-server/64869 "2016-11-03T13:27:50Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Paul\_Ainslie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paul_ainslie/32/55031_2.png) [@Paul\_Ainslie](https://discuss.elastic.co/u/Paul_Ainslie)
#### Post date: [November 3, 2016, 1:27pm UTC](https://discuss.elastic.co/t/5-0-0-alpha5-xput-mapping-response-curl-52-empty-reply-from-server/64869/1 "2016-11-03T13:27:50Z")

</div>

Why would I get an "Empty reply from server" when trying to create a mapping? Turned logging up to DEBUG and I'm not seeing anything. All the other curl commands work fine including creating a new index.

We upgraded last week to ES 5.0.0-alpha5. This exact same mapping worked fine in ES 2.4.1.

```
   ~$ curl -XPUT localhost:9200/mediaserver_v2/_mapping -d @mediaserver_v2_mapping.json -vvv
    * Hostname was NOT found in DNS cache
    * Trying 127.0.0.1...
    * Connected to localhost (127.0.0.1) port 9200 (#0)
    > PUT /mediaserver_v2/_mapping HTTP/1.1
    > User-Agent: curl/7.38.0
    > Host: localhost:9200
    > Accept: */*
    > Content-Length: 2216
    > Content-Type: application/x-www-form-urlencoded
    > Expect: 100-continue
    > 
    * Empty reply from server
    * Connection #0 to host localhost left intact
    curl: (52) Empty reply from server
```

---

<div class="post-metadata">

### Author: ![shanec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shanec/32/4004_2.png) [@shanec](https://discuss.elastic.co/u/shanec)
#### Post date: [November 4, 2016, 5:43pm UTC](https://discuss.elastic.co/t/5-0-0-alpha5-xput-mapping-response-curl-52-empty-reply-from-server/64869/2 "2016-11-04T17:43:08Z")

</div>

Alpha5 had a bug with netty4 + the `Expect: 100-continue` header. See [here](https://github.com/elastic/elasticsearch/issues/19834) for details. You have 2 options:

1. Upgrade to beta1 or later, where the bug was fixed
2. Switch to netty3 by running Elasticsearch with `bin/elasticsearch --E http.type=netty3`

---

<div class="post-metadata">

### Author: ![Paul\_Ainslie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paul_ainslie/32/55031_2.png) [@Paul\_Ainslie](https://discuss.elastic.co/u/Paul_Ainslie)
#### Post date: [November 7, 2016, 2:33pm UTC](https://discuss.elastic.co/t/5-0-0-alpha5-xput-mapping-response-curl-52-empty-reply-from-server/64869/3 "2016-11-07T14:33:59Z")

</div>

Thanks - upgrading to ES 5.0.0 did the trick!

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 10:06pm UTC](https://discuss.elastic.co/t/5-0-0-alpha5-xput-mapping-response-curl-52-empty-reply-from-server/64869/4 "2017-07-05T22:06:12Z")

</div>


