15

This is not really an issue, because the code works, but I am just curious as to why it happens.

I have the following jQuery code for an ajax post:

$.post('./add_fee_row/<?php echo $date; ?>',post, function(data){ ... });

It all works fine and dandy.

However in the Chrome Console it says: what is going on here?

Why does it say cancelled?

Everything happened as if the post was successful. Why does it say that?

(the php server code is available if needed)

I am using Google Chrome version: 17.0.942.0

Gumbo
  • 643,351
  • 109
  • 780
  • 844
Naftali
  • 144,921
  • 39
  • 244
  • 303
  • When I was working with some calls to a Sinatra web service a while back I got the same issue and never figured it out, so I'm curious too. – Chad Nov 28 '11 at 21:30
  • 1
    Seems to be yet another great update from our friends @ chromium. I started to get those cancelled messages too. Also when using jQuery. Finally got rid of those annoying deprecated ( http://stackoverflow.com/questions/7825448/webkit-issues-with-event-layerx-and-event-layery ) messages and now this :P – PeeHaa Nov 28 '11 at 21:32
  • @PeeHaa naaah i still have the deprecated messages.... – Naftali Nov 28 '11 at 21:33
  • @Neal: I upgraded to 1.7 and before that I fixed it by removing the culprits. – PeeHaa Nov 28 '11 at 21:34
  • It also can happen if you form submit via POST at the same time with XMLHTTPRequest. It's a case if you forgot to prevent default form submit but also trigger some XMLHTTPRequest at the same time. – Dmitrii Dushkin Aug 15 '23 at 14:59

2 Answers2

2

There was a bug in Chrome DevTools, it is already fixed: http://code.google.com/p/chromium/issues/detail?id=104920

vsevik
  • 9,559
  • 3
  • 19
  • 11
0

it may happen when Chrome sees that the actual data doesn’t match the headers.

If you return your answer with header type added, it shouldnt say canceled (Content-type: text/plain. for example)

You can check them by looking Event tabs - response headers.

Kemal Can Kara
  • 416
  • 2
  • 15