Showing results for 
Search instead for 
Do you mean 
Community Home Request Access Read Blogs Share Your Ideas Search Community View My Settings
Reply
Copper Super Contributor
Posts: 172
Registered: ‎07-06-2010

SDATA 401 followed by SDATA 200 HTTP request

[ Edited ]

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.

Employee
Posts: 629
Registered: ‎04-24-2009

Re: SDATA 401 followed by SDATA 200 HTTP request

Hi,

 

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

 

Thanks

 

Mike

Copper Super Contributor
Posts: 99
Registered: ‎07-04-2009

Re: SDATA 401 followed by SDATA 200 HTTP request

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

 

 


Cheers
Chris Grant
Plus Consulting
Employee
Posts: 629
Registered: ‎04-24-2009

Re: SDATA 401 followed by SDATA 200 HTTP request

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

 

Thanks

 

Mike

Employee
Posts: 27
Registered: ‎08-06-2009

Re: SDATA 401 followed by SDATA 200 HTTP request

This should be fixed in the next Xbar release.

Copper Super Contributor
Posts: 172
Registered: ‎07-06-2010

Re: SDATA 401 followed by SDATA 200 HTTP request

[ Edited ]

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.

Employee
Posts: 27
Registered: ‎08-06-2009

Re: SDATA 401 followed by SDATA 200 HTTP request

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

Highlighted
Copper Super Contributor
Posts: 172
Registered: ‎07-06-2010

Re: SDATA 401 followed by SDATA 200 HTTP request

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