-1

I have a site secured with SSL. It's a single page application. The application communicates with a back-end REST service using mostly POST operations.

The application loads perfectly fine but calling the back-end REST service fails. Using the security tab in Chrome's developer tools shows that the SSL cert is perfectly valid.

If I try to run the application in IE it works perfectly fine (i.e. the REST API calls work fine) but it just doesn't work in Chrome. If I switch off Require SSL the application works perfectly fine (but obviously not securely).

If I try to perform a GET on the back-end service by typing the URL directly into the browser this works fine in Chrome, so it's just POST operations that aren't working.

I'm scratching my head as to how to debug this. Is there another, lower-level tool I can use to discover what is going on?

There is no actual error code showing for the requests in the network tab in Chrome - just 0() on the console. This would seem to indicate that the back-end just isn't returning anything.

closed as off-topic by Michael Hampton Aug 9 '18 at 21:43

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions on Server Fault must be about managing information technology systems in a business environment. Home and end-user computing questions may be asked on Super User, and questions about development, testing and development tools may be asked on Stack Overflow." – Michael Hampton
If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    What call are you trying to make? What failure do you see? Please be specific. This description is much too vague. See also MCVE – Michael Hampton Aug 3 '18 at 12:59
0

It turns out this was happening because my code was setting an empty Authorization header which Chrome was refusing to send to the server.

See here: Similar problem on Stack Overflow

Not the answer you're looking for? Browse other questions tagged or ask your own question.