SDATA 401 followed by SDATA 200 HTTP request [ Edited ]

[elliotrodriguez]

Our working SDATA and SLX client web logs show what look like pre-auth requests being made every time the web client makes an SDATA request for data.

2014-07-17 15:48:58 W3SVC271008049 IPADDRESS GET /sdata/slx/dynamic/-/accounts where=Id%20in%20('A6UJ9A00RMWS') 5697 - 172.29.12.18 Sage 401 5 0
2014-07-17 15:48:59 W3SVC271008049 IPADDRESS GET /sdata/slx/dynamic/-/accounts where=Id%20in%20('A6UJ9A00RMWS') 5697 - 172.29.12.18 Sage 200 0 0

See the 401 status code in the first line? The above is an entry from our web client log and it happened when the user went to view Opportunity details.

Why does this occur? The web app and SDATA are working, both as the WebDLL user and are correctly configured. This seems to happen from our mobile deployment as well as from external apps using the SDATA client library assembly.

[mcessna]

Hi,

The 401 is the expected response in a challenge/response authentication scenario.

Thanks

Mike

[ChrisGrant]

In the case of xBar its doing it for every single query which does not seem right.

[mcessna]

Each new connection will include a 401. The xBar is likely creating a destroying a connection for each request.

Thanks

Mike

[NathanBaulch]

This should be fixed in the next Xbar release.

[elliotrodriguez]

Mike - why does it occur twice? Is there a way to enable pre-emptive authorization so this does not occur on every single SDATA call?

We see this in mobile, where logs show 401s and 200s for every single call.

[NathanBaulch]

I can't comment on mobile, but the PreAuthenticate flag will be enabled in the next Xbar release.

[elliotrodriguez]

Sure hope it makes its way to all requesting SDATA apps. It makes for a lot of "chatter".