najax: method jqXHR getAllResponseHeaders not implemented

[joshkg]

We just moved a project onto a new box, and I'm getting this error:

najax: method jqXHR getAllResponseHeaders not implemented

Looking at the source, I can see the notImplemented fn is first assigned to jqXHR.getAllResponseHeaders and then that is being assigned with the real getAllResponseHeaders fn:

    dfd.getAllResponseHeaders = jqXHR.getAllResponseHeaders = function getAllResponseHeaders () {
      var headers = []
      for (var key in res.headers) {
        headers.push(key + ': ' + res.headers[key])
      }
      return headers.join('\n')
    }

I'm not clear on what the scenario is when the notImplemented method would be called, since it looks like it is always being overwritten inside the request callback. Can someone clarify for me?

I don't have much insight on the new box this project is deployed on, I'm guessing that its unable to make outside requests - but wanted to understand this specific error before making that assumption.

Thanks!

[joshkg]

So the real issue as I learned is that my ajax call was being blocked by network rules (thus failing), so the najax callback on the request never gets called. It’s the library underneath (jQuery) that then calls the getAllResponseHeaders method as part of the resolution on the ajax call, but because najax overwrites that method to log “not implemented” this is why we see that message when the ajax call fails. It just so happens that the first method to get called after failure is getAllResponseHeaders. So while the “not implemented” log is entirely accurate in the narrow sense of this method, it doesn’t really explain the big picture issue which is that hey, sorry pal, the ajax call failed.

…

On Nov 22, 2018, at 3:00 PM, Jason Evans ***@***.***> wrote: +1 - Just noticing this in my local dev environment, too. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[jasonmevans]

Same here. I realized there were some API calls made during FastBoot startup that we’re failing. Addressed those, and FastBoot started working again. I get the response headers method is just stubbed out with notImplemented method, but it completely obscures the underlying Ajax failure. nAjax should rethink the impl.

…

On Fri, Nov 23, 2018 at 9:07 AM Josh ***@***.***> wrote: So the real issue as I learned is that my ajax call was being blocked by network rules (thus failing), so the najax callback on the request never gets called. It’s the library underneath (jQuery) that then calls the getAllResponseHeaders method as part of the resolution on the ajax call, but because najax overwrites that method to log “not implemented” this is why we see that message when the ajax call fails. It just so happens that the first method to get called after failure is getAllResponseHeaders. So while the “not implemented” log is entirely accurate in the narrow sense of this method, it doesn’t really explain the big picture issue which is that hey, sorry pal, the ajax call failed. > On Nov 22, 2018, at 3:00 PM, Jason Evans ***@***.***> wrote: > > +1 - Just noticing this in my local dev environment, too. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub, or mute the thread. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#66 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAe32ua_OOlFtWj0qQOumAOHruAncJP_ks5uyCszgaJpZM4XIUgh> .