Login.js transaction number

[yavery]

Hi,

I just grabbed the latest version (04/30) of the LGPL 8.2p framework (upgrading from 8.2p 04/02)
and this updated version is breaking our backend because it is now encoding a new "isc_tnum"
query parameter to the the login request ...

Our backend is validating the URLs and doesn't support that extraneous parameter. Is there a way
to have that new additional parameter disabled ?

Isn't the 8.2p track meant for bug fixes only ? What bug is this new query parameter fixing ? Seems
more like an enhancement to me ...

Thanks,

[Isomorphic]

Most likely this is because of the need to work around this nasty Chrome bug by moving the transaction number out of the URL and into the transaction itself.

How is this impacting you?

[yavery]

We have a servlet filter in place that validates received URL query strings. When it receives
a URL query strings that isn't valid, it throws an exception. In this case, not being valid is the
fact that this URL contains a query string parameter (isc_tnum) which is not expected.

I can modify our servlet filter to let this go thru, but before doing so, I'd like to know if there
are any other query string parameters that could get appended in any situation (that weren't
present in 8.2p as of the 04/02 version) ?

Thanks,

[Isomorphic]

Our changes involved moving the isc_tnum out of the URL - what kind of server contact is this that you're doing? Through a DataSource, direct to RPCManager, useSimpleHttp or not, etc?

[yavery]

I use the following :

  RPCManager.sendRequest
  ({
    actionURL : 'tpm/Acme/views/Login.js',
    showPrompt : true,
    httpMethod : 'GET',
    params : null,
    useSimpleHttp : true,
    bypassCache : true,
    evalResult : true,
    evalVars : { viewLoader : viewLoader },
    callback :
      function(rpcResponse, data, rpcRequest)
      {
        // ...
        viewLoader.fireCallback(callback, 'rpcResponse, data, rpcRequest', [ rpcResponse, data, rpcRequest ]);
      }
  });

The query that ends up being sent to the server has the following URL (from Chrome debugger) :

http://......./tpm/Acme/views/Login.js?isc_tnum=0

That 'isc_tnum' query string parameter that gets added triggers a server side validation we have
that doesn't allow for any query string parameters for that particular URL invoke ...

In version 8.2p from 04/02, that same RPCManager call would simply invoke the URL untouched,
without that extraneous query string parameter.

Does this help figuring out what's going on ?

Thanks,

[yavery]

Hi,

Were you able to identify why this 'isc_tnum' query parameter is getting appended to my request URL ?

Thanks,

[Isomorphic]

Hi
We've just tracked this one down. Will be fixed in the next nightly build

Regards
Isomorphic Software

[yavery]

Looks good now. Thanks!