This is a warning to you all that the X-SecondLife-Owner-Name header is not reliable after sim crossings - or at least hasn't been for me. On the first call after each sim-crossing I have received "
Loading...)" in this header rather than, obviously, the owner's name. (On closer examination, 1 of 7 sim-crossings in the test-run I've just done actually provides the correct data). What I haven't recorded so can't report is how long after the crossings the Http requests were made.My requests are being sent every 10s from an LSO-compiled HUD script, as GETs and with just "no body" in the body (it's a placeholder for now). The very simple PHP target calculates global position but otherwise just dumps the headers straight into MySQL (owner name, owner key, globalX, globalY, sim, rotation and velocity) and returns 'done' as the body of the response, just so the response doesn't time-out.
All the other data appears fine, just the owner's name not yet available from SL. The obvious workaround is just to use the owner's key, of course, but I thought I'd bring this to everyone's attention.