Results 1 to 6 of 6

Thread: HTTP response 204 different in FF vs Chrome

    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1

    Default HTTP response 204 different in FF vs Chrome

    I have an application that given this:

        clientValidation: true,
       url: ...,
       scope: me,
       success: me.onSuccess,
       failure: me.onFailure
    When the response is a 204 (no content), in Chrome enters onSuccess() (this is right), and in Firefox enters onFailure() (I find this wrong).

    Someone noticed this too?

    ExtJS version

  2. #2


    I believe my report was not very good...

    Firefox: 47.0
    Chromium: 51.0.2704.79 Ubuntu 15.10 (64-bit)

    Actually is Firefox vs Chromium, but really doesn't matter since it is Firefox the one with the -maybe- wrong behaviour.

    I dove a bit down to here:




  3. #3


    Hi Alfonso,

    Please provide a test case demonstrating the problem so we can arrive at a solution for you.

    Ideally, a test case would be:

    1. A simple example using the minimal amount of code that shows an issue in a Sencha product.
    2. Locally runnable
    3. Reproducible
    4. Isolated from third party products
    5. Without requirements to access any remote resources
    6. All data needed available to be loaded locally (using a JSON or XML flat file)
    7. Preferably at']fiddle.

    If your issue is specific to a browser or OS, please note that. Screen caps and Screencasts created by products like Jing may also be very helpful in tracking down any issues


    Kevin Jackson
    Sencha Support Team

  4. #4


    Hi, Kevin.

    Thanks for your answer. I can not comply with your request because it is something that requires a REST server. If I am not wrong, does not allow it, isn't it?

    Anyway, I deployed an AWS micro instance so you can try it: (be patient, it is a micro instance and is very slow... and with development deploy).
    The login credentials are admin:admin.
    Try it with Chrome, try it with Firefox. Same code, different outcome (the app is very early build, so just only expect the login error, or nothing .
    You can take a look at LoginController:27 where is the submit, in the same controller are the handlers onSuccess and onFailure.
    If you see my snapshots, I nailed it down to "processResponse".

    Test it just take you 20 seconds
    If it works for you, then awesome!

    Tell me when you don't need the deployed app so I shutdown it (and save money :P)

  5. #5


    I was able to see the issue Could you send me the code so I can pass it along to the engineers?

    Kevin Jackson
    Sencha Support Team

  6. #6


    Oh! Sorry, I forgot to write the URL of the source code! It is here:

    And this is the LoginController:

    And this the Login view:

    I had some issues with CORS and still is not configured Can only be executed from the same tomcat in Eclipse (client+server). But I leave you the deployed AWS instace for a while if you want it.

    Thank you!

Similar Threads

  1. REST DELETE 405 HTTP response
    By Phoenicoperus in forum Ext: Q&A
    Replies: 5
    Last Post: 15 Apr 2014, 4:45 AM
  2. Loading a Store With an HTTP Response
    By UGA_Zimma in forum Ext 3.x: Help & Discussion
    Replies: 2
    Last Post: 21 Aug 2009, 5:18 AM
  3. [2.0.2][CLOSED] HTTP 204 response bug
    By rstuart in forum Ext 2.x: Bugs
    Replies: 30
    Last Post: 14 May 2008, 1:50 AM
  4. HTTP Response Code
    By KittyKat13 in forum Ext 1.x: Help & Discussion
    Replies: 6
    Last Post: 3 Oct 2007, 12:49 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts