AJAX POST content-type Warning

[visoft]

I have a link that does a POST, e.g.

link_to "Add", my_url(obj), :method => :post, :remote => :true

In my Cucumber output I get the message:

content-type missing in HTTP POST, defaulting to application/octet-stream

According to the docs, this warning can be muted by setting the following:

networkRequest.setHeader(QNetworkRequest::ContentTypeHeader, "application/octet-stream");

If you don't want to or can't add it, is there another way to stop this warning from showing up?

Thanks,
-Damien

[itsmeduncan]

👍

[ValeriiVasin]

I have similar issue.

[mhoran]

I actually think this is a Rails UJS issue, not something that can be fixed in capybara-webkit. The docs you point out are for when making POST requests from within Qt. However, the error your're getting is from testing the action of UJS. Here are the headers from a UJS action:

Accept:*/*
Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3
Accept-Encoding:gzip,deflate,sdch
Accept-Language:en-US,en;q=0.8
Connection:keep-alive
Content-Length:0
Cookie:redacted
Host:redacted
Origin:redacted
Referer:redacted
User-Agent:Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7
X-CSRF-Token:QImL5N0WkDYOo/XNcwrR4IA0eOT9xCF5U2bl1h8QGJA=
X-Requested-With:XMLHttpRequest

Note that there is no Content-Type header. capybara-webkit (really, QWebPage) is handling the POST via JavaScript, but because the UJS helpers don't set the header, it defaults to application/octet-stream. We don't want (and probably can't) to set the default header to application/octet-stream, as this may cause unexpected side-effects.

Hope this helps.

[visoft]

It's not that big of a deal. I don't think capybara-webkit should set the header; I was just hoping there was a way to keep the warnings out of my Cucumber output. I suppose a work-around would be to set the header in UJS. I think I tried hooking into the AJAX send, but wasn't able to get the warning to go away that way, but honestly I don't remember... Thanks for taking the time to look into the issue.

[dtuite]

I have the same problem and it's actually causing intermittent failures in my cucumber specs.

You can see that the spec fails here when the content type is missing:

  @javascript @favourite-concept
  Scenario: Favouriting a Concept   # features/suggestion.feature:41
    Given I am a signed in user     # features/step_definitions/registration_steps.rb:1
http://connect.facebook.net/en_GB/all.js|30|The "fb-root" div has not been created, auto-creating
    When I suggest "apple"          # features/step_definitions/suggestion_steps.rb:1
    And I click that concept's star # features/step_definitions/suggestion_steps.rb:83
content-type missing in HTTP POST, defaulting to application/octet-stream
    Then it should be favourited    # features/step_definitions/suggestion_steps.rb:87
      expected css "li.concept.fav" to return something (RSpec::Expectations::ExpectationNotMetError)
      ./features/step_definitions/suggestion_steps.rb:88:in `/^it should be favourited$/'
      features/suggestion.feature:45:in `Then it should be favourited'

But then I run the same spec 2 seconds later and it passes:

  @javascript @favourite-concept
  Scenario: Favouriting a Concept   # features/suggestion.feature:41
    Given I am a signed in user     # features/step_definitions/registration_steps.rb:1
http://connect.facebook.net/en_GB/all.js|30|The "fb-root" div has not been created, auto-creating
    When I suggest "apple"          # features/step_definitions/suggestion_steps.rb:1
    And I click that concept's star # features/step_definitions/suggestion_steps.rb:83
    Then it should be favourited

The line where the POST request is sent in my app is here:

    $.post("/favourites", { concept_id: @id }, postSuccess, "json")

I'll have a look at fixing this by setting the content type and add an update.

[emeraldMaster]

hi, I have the same issue! :(

[georges]

Same here. following thread.

[i-am-logger]

Following thread, same issue here

[latensified]

Yep.

[andreacfm]

same here. following

[mhoran]

Is this actually causing issues for anyone, or is it simply the warning that is causing concern? Last time I checked, this issue was caused by Rails omission of a content type header. Without changing Rails UJS, there's not much that can be done on our side.

[davesmylie]

For me it was more annoyance - there were so many of these messages on the screen that it made it hard to see what tests were passing/failing.

[aratak]

Same after latest update. Following

[rheaton]

+1

[santry]

For those of you using link_to with remote: true and method: post you can manually set the Content-Type header to silence the warning:

CoffeeScript:

# Set Content-Type on XHR POST requests so Qt stops complaining
$('a[data-remote="true"]').bind 'ajax:beforeSend', (event, xhr, settings) ->
  if settings.type == 'POST'
    xhr.setRequestHeader('Content-Type', 'application/x-www-form-urlencoded')

JavaScript:

$('a[data-remote="true"]').bind('ajax:beforeSend', function(event, xhr, settings) {
  if (settings.type == 'POST') {
    xhr.setRequestHeader('Content-Type', 'application/x-www-form-urlencoded');
  }
});

Of course you can adjust the jQuery selector as needed to reduce the scope of remote links that are affected.

jquery-ujs should probably be doing this itself, so when I get a chance I'll put together a pull request for them.