# Changing drop\_receiving\_element behavior to make a GET request instead of POST

**URL:** <https://www.ruby-forum.com/t/changing-drop-receiving-element-behavior-to-make-a-get-request-instead-of-post/152358>\
**Category:** Rails\
**Created:** [November 3, 2008, 5:16am UTC](https://www.ruby-forum.com/t/changing-drop-receiving-element-behavior-to-make-a-get-request-instead-of-post/152358 "2008-11-03T05:16:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![evan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/54ee81/32.png) [@evan](https://www.ruby-forum.com/u/evan)\
**Post date:** [November 3, 2008, 5:16am UTC](https://www.ruby-forum.com/t/changing-drop-receiving-element-behavior-to-make-a-get-request-instead-of-post/152358/1 "2008-11-03T05:16:39Z")

</div>

Is it possible to specify which HTTP method to use in the  
drop\_receiving\_element helper? I’m trying to follow REST best  
practices in my app. On one page I have the user drop an icon into an  
area which calls the “new” representation of a particular resource.  
However, drop\_receiving\_element sends the request as POST which is not  
allowed. How can I change the method so it makes a GET request?

---

<div class="post-metadata">

**Author:** ![evan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/54ee81/32.png) [@evan](https://www.ruby-forum.com/u/evan)\
**Post date:** [November 6, 2008, 5:22pm UTC](https://www.ruby-forum.com/t/changing-drop-receiving-element-behavior-to-make-a-get-request-instead-of-post/152358/2 "2008-11-06T17:22:23Z")

</div>

For those curious, I solved this problem by abandoning the  
drop\_receiving\_element helper and writing my own Ajax.Updater (see  
Prototype documentation) code on the page. Ajax.Updater takes a  
“method” option which allows you to specify get, post, put, delete,  
etc.