Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Have you tried</p> <pre><code>$.ajax({ url: this.hostName + url, type: 'POST', headers: { 'X-CSRF-Token': $('meta[name="csrf-token"]').attr('content') } data: { param : 'something' }, dataType: 'json' }); </code></pre> <p>And then in your controller params[:param] will give you 'something'.</p> <p>If you are interested to know why you need all that X-CSRF-Token stuff, <a href="http://guides.rubyonrails.org/security.html#cross-site-request-forgery-csrf" rel="nofollow">this</a> is a good read. Basically, Rails automatically includes that token in your page to keep your application safe. If you inspect any page of your site, you'll see in the head of your HTML document something like this:</p> <pre><code>&lt;meta content="guma1QdmO9Tn9SB4yV4DonkY4xf4Sy6lIvrFyHIaR1U=" name="csrf-token"&gt; </code></pre> <p>This is created by the line <code>&lt;%= csrf_meta_tags %&gt;</code> included in your <code>application.html.erb</code> file.</p> <p>Rails automatically includes this token in regular non-GET requests to keep them safe. But with javascript and ajax, you have to do this manually by searching the DOM for the token with the jQuery function <code>$('meta[name="csrf-token"]'</code>.</p> <p>Now, this isn't very efficient because you are searching for that token every time you are making a request. So what you should do, is use ajaxSetup, like this:</p> <pre><code>$.ajaxSetup({ type: 'POST', headers: { 'X-CSRF-Token': $('meta[name="csrf-token"]').attr('content') } dataType: 'json' }); </code></pre> <p>And now, whenever you want to send a request, all you need is this:</p> <pre><code>$.ajax({ url: this.hostName + url, data: { param : 'something' } }); </code></pre> <p>EDIT: Ah, I see. What do you get when you do <code>alert(this.hostName + url)</code>? And how are you declaring your routes? Because if I remember correctly, you can use relative urls instead of absolute urls, you don't need the root part. Here's an example:</p> <pre><code># routes.rb post "relative_url" =&gt; 'controller#action' # file.js $.ajax({ url: "relative_url", data: { param : 'something' } }); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PORouting error: No route matches [OPTIONS]
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAshitaka
    1. USAshitaka
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORouting error: No route matches [OPTIONS]
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    1. COThanks for the extensive answer, but it still does not solve my problem. When I add the header in, I get a routing error (stated above). Instead of `Started POST /data', I get an error saying 'Started [OPTIONS] /data' and no route matches [OPTIONS].
      singulars
      1. PO
      1. USrabid_zombie
    2. COSee my edited answer.
      singulars
      1. PO
      1. USAshitaka
    3. COSame issue but this didn't solve it. My ajax call is a cross-domain call (with CORS) and works as long as I don't set the headers options in the ajax setup. I get Started [OPTIONS] ... with no route matching.
      singulars
      1. PO
      1. USMatt Smith
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload