# Routing a PUT request from Notehub

**URL:** <https://discuss.blues.com/t/routing-a-put-request-from-notehub/415>\
**Category:** Notehub.io\
**Created:** [September 6, 2021, 2:28pm UTC](https://discuss.blues.com/t/routing-a-put-request-from-notehub/415 "2021-09-06T14:28:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![PostThis](https://avatars.discourse-cdn.com/v4/letter/p/5f8ce5/32.png) [@PostThis](https://discuss.blues.com/u/PostThis)\
**Post date:** [September 6, 2021, 2:28pm UTC](https://discuss.blues.com/t/routing-a-put-request-from-notehub/415/1 "2021-09-06T14:28:34Z")

</div>

@bsatrom @RobLauer @gwolff

I have another route problem to check into. I can make POST requests without issue. But I can’t seem to perform a PUT request. This could be operator error, but I have triple checked everything. Is PUT possible from notehub? Under Route Type, I am using “General HTTP/HTTPS Request/Response”. Should there be a separate PUT option?

---

<div class="post-metadata">

**Author:** ![bsatrom](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/bsatrom/32/3_2.png) [@bsatrom](https://discuss.blues.com/u/bsatrom)\
**Post date:** [September 6, 2021, 2:49pm UTC](https://discuss.blues.com/t/routing-a-put-request-from-notehub/415/2 "2021-09-06T14:49:55Z")

</div>

Hey Greg,

Currently, the “General HTTP/HTTPS Request/Response” type is POST only. I’m happy to add a feature request to support PUT requests via this or a new route type. To help us understand the need, are you routing to a location that accepts data only via PUT requests, or is this a service you mange?

---

<div class="post-metadata">

**Author:** ![PostThis](https://avatars.discourse-cdn.com/v4/letter/p/5f8ce5/32.png) [@PostThis](https://discuss.blues.com/u/PostThis)\
**Post date:** [September 6, 2021, 4:56pm UTC](https://discuss.blues.com/t/routing-a-put-request-from-notehub/415/3 "2021-09-06T16:56:54Z")

</div>

Routing to a service that accepts PUT and POST requests. PUT would definitely help avoid exploding database size. Oh and without PUT, I have to create size-able workarounds.

---

<div class="post-metadata">

**Author:** ![devElert](https://avatars.discourse-cdn.com/v4/letter/d/8e8cbc/32.png) [@devElert](https://discuss.blues.com/u/devElert)\
**Post date:** [February 21, 2024, 12:38am UTC](https://discuss.blues.com/t/routing-a-put-request-from-notehub/415/4 "2024-02-21T00:38:04Z")

</div>

We ran into this as well. Some services accept a method override header:

```auto
headers: { 'X-Http-Method-Override': 'PUT' }

```

The header indicates which method is intended, even if it’s not the one actually used.