[ 
https://issues.apache.org/jira/browse/CB-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15029710#comment-15029710
 ] 

Durss commented on CB-2415:
---------------------------

I've just lost days searching everywhere, trying to fix it in many different 
ways before ending up here...
If the problem is known as well as its fix, why isn't it fixed almost 3 years 
later.? :/

With angular there is no async option to $http and using anything else than 
$http would break the architecture of the project.
Changing the server headers/return code isn't an option for people using 
existing APIs they don't have hands on (and breaks the standards).

I'll see what i can do at the native level but the goal of using cordova was to 
actually avoid touching any native stuff (that will probably be broken again 
after each project's generation..).

I hope this will be fixed someday (soon?^^).

Have a good day !

> On iOS the ajax error/fail callback is not called after server returns error 
> code 401/unauthorized
> --------------------------------------------------------------------------------------------------
>
>                 Key: CB-2415
>                 URL: https://issues.apache.org/jira/browse/CB-2415
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 2.2.0
>         Environment: OSX 10.8.2, Xcode 4.5.1, iOS Simulator 5.0, 5.1, 6.0, 
> cordova 2.2
>            Reporter: Zach White
>            Assignee: Tobias Bocanegra
>              Labels: 401, BasicAuth, core
>
> I am seeing the same issue as reported in 
> [CB-2284|https://issues.apache.org/jira/browse/CB-2284] also in iOS. Ajax 
> calls with Authorization header set are not returning but are timing out when 
> the authorization credentials are invalid.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to