On Jun 25, 2008, at 7:37 AM, Mark wrote:
Well, it's been a few months since a posted this message and filed
this bug: https://bugs.webkit.org/show_bug.cgi?id=18539
We haven't been able to find a work around at all, every single
thing we do doesn't work. So I'm making a plea again, can
The bug is in the php tool, not in webkit. From the RFC (rfc1341 http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html)
:
boundary := 0*69bchars bcharsnospace
bchars := bcharsnospace /
bcharsnospace :=DIGIT / ALPHA / ' / ( / ) / + /
_
/ , / - / . / / / : / = / ?
'+'
It used to be worse! At one time we originally allowed all the legal values
for base64 encoding in the boundary string:
http://trac.webkit.org/projects/webkit/changeset/20074
But then it was changed:
https://bugs.webkit.org/show_bug.cgi?id=13352
I should have probably said I don't actually code myself. I merely design
the software so I'll have to pass on all this information to my coder as
some of it is a bit above my head..
What I don't understand is, is the fault is with the script somehow. Why did
the exact same scripts work perfectly
Before Safari 3, the boundary string was always:
--0xKhTmLbOuNdArY
This apparently doesn't violate any assumptions made by the scripts you use.
As for other browsers, you'd have to test them yourself, but apparently they
never use + characters in their multipart/form-data boundaries.
Hi Mark,
On Apr 16, 2008, at 10:32 AM, Mark Pauley wrote:
The bug is in the php tool, not in webkit. From the RFC (rfc1341 http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html)
:
boundary := 0*69bchars bcharsnospace
bchars := bcharsnospace /
bcharsnospace :=DIGIT / ALPHA / ' / (
The issue appears to be that when WebKit sent a multipart/form-data boundary
with a + character in it, the server-side software wouldn't decode the
request properly. (When there was no + character in the form boundary,
everything worked fine.)
Mark didn't say what software he was using on the
I don't have access to the script, but I can get the source. The problem is
this form demo from jmbsoft is installed of thousands of thousands of sites
that my software needs to submit to, and thus since this webkit bug was
introduced my software has real problems with all these sites. All these
Mark,
You should test my theory (it's only a theory at this point) to make sure it's
correct before you assume that you'll have to update the script thousands of
web sites.
If it is a bug in the script, perhaps you should take the opportunity to devise
a way to push out future updates in case
Scott Thompson [EMAIL PROTECTED] wrote:
On Apr 11, 2008, at 7:37 PM, David Kilzer wrote:
The best thing you could do is to file a bug on
https://bugreport.apple.com/
and attach source for a project that reproduces the issue, along
with details
steps to reproduce the issue. If you
Hi guys, many thanks for your advice. I'll check out the wireshark thing for
sure. In the meantime I have managed to cobble together a demo so you can
see hopefully the bug:
Please go here: http://demo.jmbsoft.com/cgi-bin/ags/submit.cgi
Enter the following information:
Username, Password: Leave
Hi Mark,
The best thing you could do is to file a bug on https://bugreport.apple.com/
and attach source for a project that reproduces the issue, along with details
steps to reproduce the issue. If you don't have an Apple Developer Connection
(ADC) membership, sign up for a free online membership
On Apr 11, 2008, at 7:37 PM, David Kilzer wrote:
The best thing you could do is to file a bug on https://bugreport.apple.com/
and attach source for a project that reproduces the issue, along
with details
steps to reproduce the issue. If you don't have an Apple Developer
Connection
(ADC)
13 matches
Mail list logo
