[Crossposting to jmeter-user and jmeter-dev, following Mike S's
lead. Mike, was it your intention to move this to only
jmeter-dev?]
On Tue, Aug 13, 2002 at 09:13:28AM -0400, Mike Stover wrote:
> I'm a little concerned about the multipart form issue you raise - JMeter has always
>in the past
> correctly parsed multipart forms as multipart forms - so I'm wondering why your
>request
> doesn't work. Are you doing something weird? Normally, mulitpart forms are created
>when
> browsers upload files, with HTML like so: <form action="upload.jsp" method="POST"
> enctype="multipart/form-data"><input type="File" ...></form>.
It is indeed a file upload. I don't know whether the application
does anything weird. I didn't write it; I was just told,
"load-test it". I just dove into the RFCs last night while
tracking this down.
Maybe what's weird is that I checked a radio button that doesn't
require a file to actually be uploaded ("use previous image", as
opposed to "use the image I'm about to upload")...
I've attached a log of the transaction (hooray for Ethereal!),
and also a hex dump for anyone who wants to read it directly in
their mail client. Byte-for-byte, except that I've removed the
reply body (dunno if there's anything proprietary in there; don't
want to take the time to ask; and it's not important anyway, just
a Java stack trace plus elaboration from the application itself).
On Tue, Aug 13, 2002 at 10:31:16AM -0400, Mike Stover wrote:
> I've made a change that prevents JMeter from encoding the values sent by the browser.
Cool! Thanks!
> It's
> not a perfect solution yet - if you change things in the GUI (after recording is
>done), it can
> mess things up.
Which GUI; JMeter's or the target app's? If the latter, I've
been assuming that; isn't it *necessarily* the case? In either
case, how could merely URL-encoding prevent it? Could you give
an example?
> The problem is, some values
> need to be encoded, and some should not be, but detecting the difference will
>require some
> work.
Why? Surely the browser has already encoded the values that need
it -- and only those. Why does the proxy have to even think
about it?!? Why is it not sufficient -- and indeed, the only
theoretically correct approach -- for the proxy to pass along
precisely the bytes it received?
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont. [EMAIL PROTECTED]
| | /
Anyone who swims with the current will reach the big music steamship;
whoever swims against the current will perhaps reach the source.
- Paul Schneider-Esleben
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
