-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aryeh,
On 3/2/2010 7:12 PM, Aryeh M. Friedman wrote:
Christopher Schultz wrote:
If that string above is your entire POST request body, then it's not
properly formatted. Instead, it should be:
call=8347812459870132405987234985023450987
or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aryeh,
On 3/2/2010 1:51 AM, Aryeh M. Friedman wrote:
Yes we are and thats why I probably mistook the effect of it doing that
as a side effect instead of a designed in feature... now that being said
we have used that content day since the first few
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aryeh,
On 3/2/2010 1:51 AM, Aryeh M. Friedman wrote:
Yes we are and thats why I probably mistook the effect of it doing that
as a side effect instead of a designed in feature... now that being said
we have used that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aryeh,
On 3/2/2010 2:20 PM, Aryeh M. Friedman wrote:
It gets null's on POST's only but only from the new input format (there
are parts of the app that still use the old format and they work fine)
Is this a new client, or just a new data format?
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aryeh,
On 3/2/2010 2:20 PM, Aryeh M. Friedman wrote:
It gets null's on POST's only but only from the new input format (there
are parts of the app that still use the old format and they work fine)
Is this a new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aryeh,
On 3/2/2010 3:48 PM, Aryeh M. Friedman wrote:
Christopher Schultz wrote:
Is this a new client, or just a new data format? Mark's suggestion that
you may be using POST without the proper Content-Type would result in
getting null for this
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aryeh,
On 3/2/2010 3:48 PM, Aryeh M. Friedman wrote:
Christopher Schultz wrote:
Is this a new client, or just a new data format? Mark's suggestion that
you may be using POST without the proper Content-Type
Aryeh M. Friedman wrote:
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aryeh,
On 3/2/2010 3:48 PM, Aryeh M. Friedman wrote:
Christopher Schultz wrote:
Is this a new client, or just a new data format? Mark's suggestion
that
you may be using POST without the
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aryeh,
On 3/2/2010 3:48 PM, Aryeh M. Friedman wrote:
Christopher Schultz wrote:
Is this a new client, or just a new data format? Mark's suggestion that
you may be using POST without the proper Content-Type
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aryeh,
On 3/2/2010 4:05 PM, Aryeh M. Friedman wrote:
Aryeh M. Friedman wrote:
Aryeh M. Friedman wrote:
Christopher Schultz wrote:
I know this sounds silly, but we're getting down to the
grasping-at-straws level, here, so bear with me: have you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aryeh,
On 3/2/2010 4:12 PM, Aryeh M. Friedman wrote:
Also forgot to mention I already refactored the servlet to use pure
hex encoding (namely we convert the entire request into a hex string
so for example a old format message of
On 02/03/2010 21:04, Aryeh M. Friedman wrote:
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aryeh,
On 3/2/2010 3:48 PM, Aryeh M. Friedman wrote:
Christopher Schultz wrote:
Is this a new client, or just a new data format? Mark's suggestion that
you may be using
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aryeh,
On 3/2/2010 4:05 PM, Aryeh M. Friedman wrote:
Aryeh M. Friedman wrote:
Aryeh M. Friedman wrote:
Christopher Schultz wrote:
I know this sounds silly, but we're getting down to the
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aryeh,
On 3/2/2010 4:12 PM, Aryeh M. Friedman wrote:
Also forgot to mention I already refactored the servlet to use pure
hex encoding (namely we convert the entire request into a hex string
so for example a old format
Pid wrote:
On 28/02/2010 02:00, Aryeh M. Friedman wrote:
I am refactoring a servlet we have used successfully for several years
now to accommodate input that does not amen itself to
HttpServletRequest.getParameter()... The only way it seems to be to
handle our particular input (the
On 01/03/2010 08:01, Aryeh M. Friedman wrote:
Pid wrote:
I want to preserve the single handler design but since getParameter
barfs on our new input format and there is no unified raw input reader
the only thing I can think of is make it so doGet and doPost use
request.getQueryString() and
Mark Thomas wrote:
On 01/03/2010 08:01, Aryeh M. Friedman wrote:
Pid wrote:
I want to preserve the single handler design but since getParameter
barfs on our new input format and there is no unified raw input reader
the only thing I can think of is make it so doGet and doPost use
On 28/02/2010 02:00, Aryeh M. Friedman wrote:
I am refactoring a servlet we have used successfully for several years
now to accommodate input that does not amen itself to
HttpServletRequest.getParameter()... The only way it seems to be to
handle our particular input (the nature/format of the
I am refactoring a servlet we have used successfully for several years
now to accommodate input that does not amen itself to
HttpServletRequest.getParameter()... The only way it seems to be to
handle our particular input (the nature/format of the input is covered
by an NDA so I can not
19 matches
Mail list logo