Tavern on the Meta

Someone explain to me how the exact same POST request with the exact same params to the exact same URL with the exact same auth can fail on one device and succeed on another.

aaaargh

Hobo Sapiens

Arrgghh! Where do these people come from? This guy has posted four questions, all just with a valid JSON object and a problem description of 'it's not working'. Please, please, please NUKE!

1:14 AM

Idiot of the day: My mom's ex-boss.

> Correct me if I'm not mistaken.

Hobo Sapiens

Oops - one of his questions actually has some javascript. Lousy question though

1:30 AM

+21/-2 for me on LH

1:40 AM

@AlfredYerger $e^{\tau i} = 1$ — bjb568 9 secs ago

Jan Dvorak

1:58 AM

@UndotheSnowman caching, user agent, IP filters (an auth token could be bound to an IP), ISP's stupid proxies, server-side randomness, network randomness, server relying on a service with dubious availability (throttled)...

@JanDvorak you forgot the most important of all: reasons

►

2:20 AM

@JanDvorak Not caching, not user agent, not IP filters, not ISP, and not network randomness. It's reproducible, on my network. Feeding Postman all the headers from either session makes it work with the 32-bit generated JSON:

{"obs":[{"concept":"5090AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA","value":"132","obsDatetime":"2014-12-23T19:08:12.472-0700","person":"f149555e-69c5-4129-9b8d-57a9f47d248a"}], "encounterType":"67a71486-1a54-468f-ac3e-7091a9a79584","patient":"f149555e-69c5-4129-9b8d-57a9f47d248a","encounterDatetime":"2014-12-23T19:08:12.480-0700","location":"aff27d58-a15c-49a6-9beb-d30dcfc0c66e"}

And not with the 64-bit generated JSON:

{"encounterDatetime":"2014-12-23T19:02:36.479-0700","encounterType":"67a71486-1a54-468f-ac3e-7091a9a79584","location":"aff27d58-a15c-49a6-9beb-d30dcfc0c66e","patient":"f149555e-69c5-4129-9b8d-57a9f47d248a","obs":[{"person":"f149555e-69c5-4129-9b8d-57a9f47d248a","value":"132","obsDatetime":"2014-12-23T19:02:36.478-0700","concept":"5090AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA"}]}

And ordering them the same and feeding them to diff says that only the timestamps are off

Huh, feeding the webservice either ordered one makes it choke

But order doesn't matter in JSON, right? :/

@UndotheSnowman `mm? reproducible how?

@Braiam as in it happens every time

@UndotheSnowman I meant steps...

order doesn't matter if the app parses it as document

(umm, actually I don't know if JSON parsing is similar to XML parsing or not, I'll research first)

@Braiam oh, putting the request headers from the 64bit request into Postman, then giving it the 32-bit JSON works but not the 64-bit JSON.

this can't be right

2:29 AM

okay, I'm confused since I don't see why it won't work

@UndotheSnowman ehhh? that made no sense to me

are different builds/version right?

@Braiam same version. Same app. Different devices. One 32-bit, one 64-bit.

Related question: Is the sequence of the values matter in JSON object?

@UndotheSnowman I bet there's some arch only bug somewhere

@Braiam I'm thinking it's a bug on serverside. It shouldn't care about JSON order :P

2:34 AM

meh, both should produce the same JSON anyways if they use the same functions

probably, but it shouldn't matter.

3:23 AM

►

lel

> All browsers support javascript, except when they don't.

4:05 AM

^ My progress on caching with DevDoodle

notice the gzip too

Wait… what's the difference between content and transfer encoding?

in The Junk Drawer on The Stack Exchange Network Chat, 2 mins ago, by J. Musser

> Any reasons for UV? ... or is this a popularity contest? — J. Musser just for fun

@bjb568 The level of zippiness, transfer encoding is for transfers, content encoding is just for the content.

@bjb568 wat

y u talking to urself

4:20 AM

coz

user259867

SE encourages answering own questions.

@Behaviour with 'wat' ?

lol

user259867

This is how you recognize avid SE users IRL. They ask, answer themselves, and later accept.

2

They also close people as not constructive.

#StarTrollz

4:23 AM

cv-pls stackoverflow.com/q/1567207/1849664

user259867

SPAM drupal.stackexchange.com/q/141603/36774

Closes the star troll as not constructive

gone

@Behaviour gone

SmokeDetector

4:35 AM

[ SmokeDetector ] All-caps title: FORGOT ID CARD PROVIDE TEMPORARY ID CARD by user13946 on ell.stackexchange.com

// This determines if the browser will accept gzip
var raw = !req.headers['accept-encoding'] || req.headers['accept-encoding'].indexOf('gzip') == -1 || req.headers['accept-encoding'].indexOf('gzip;q=0') != -1;
// Is it good enough?

@bjb568 just do it the SE way, offer gzip always and wait