[MAGNOLIA-2103] Can't Create New Paragraph With Safari 3.1 Created: 08/Apr/08  Updated: 17/Mar/09  Resolved: 08/Jul/08

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 3.5.4
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Sean McMains Assignee: Philipp Bärfuss
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Tested with Safari Version 3.1 (5525.13) and WebKit r31667


Attachments: Text File 2103.patch    
Issue Links:
duplicate
is duplicated by MAGNOLIA-2118 Magnolia - Safari 3.1 incompatible (c... Closed
relation
is related to MAGNOLIA-540 Replacing default multipart filter im... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

To reproduce:

1. Using Safari, Click the "New Paragraph" button on a Magnolia page
2. Select a paragraph type

Expected result:

An editor window will open for the new paragraph.

Actual result:

Magnolia throws an error:

{{

{ java.io.IOException: Corrupt form data: premature ending com.oreilly.servlet.multipart.MultipartParser.<init>(MultipartParser.java:205) com.oreilly.servlet.MultipartRequest.<init>(MultipartRequest.java:222) info.magnolia.cms.filters.CosMultipartRequestFilter.parseParameters(CosMultipartRequestFilter.java:94) info.magnolia.cms.filters.CosMultipartRequestFilter.doFilter(CosMultipartRequestFilter.java:81) info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71) info.magnolia.cms.security.BaseSecurityFilter.doFilter(BaseSecurityFilter.java:60) info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71) info.magnolia.cms.security.LogoutFilter.doFilter(LogoutFilter.java:81) info.magnolia.cms.filters.OncePerRequestAbstractMgnlFilter.doFilter(OncePerRequestAbstractMgnlFilter.java:62) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71) info.magnolia.cms.security.auth.login.LoginFilter.doFilter(LoginFilter.java:76) info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71) info.magnolia.enterprise.registration.RegistrationFilter.doFilter(RegistrationFilter.java:54) info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71) info.magnolia.cms.filters.ContentTypeFilter.doFilter(ContentTypeFilter.java:73) info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71) info.magnolia.cms.filters.ContextFilter.doFilter(ContextFilter.java:72) info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70) info.magnolia.cms.filters.MgnlFilterChain.doFilter(MgnlFilterChain.java:71) info.magnolia.cms.filters.CompositeFilter.doFilter(CompositeFilter.java:64) info.magnolia.cms.filters.AbstractMgnlFilter.doFilter(AbstractMgnlFilter.java:70) info.magnolia.cms.filters.MgnlMainFilter.doFilter(MgnlMainFilter.java:98) info.magnolia.cms.filters.MgnlMainFilter.doFilter(MgnlMainFilter.java:195) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) }}

}



 Comments   
Comment by Sean McMains [ 08/Apr/08 ]

This turns out to only affect Mac OS 10.5, and looks to actually be a problem with Safari, rather than Magnolia (though Magnolia could probably handle the goofy condition a little more gracefully).

Have submitted a bug to the WebKit team here:

http://bugs.webkit.org/show_bug.cgi?id=17868

Comment by Magnolia International [ 09/Apr/08 ]

I'll assign this to 4.0 for now, as it will def. be fixed with the new gui, but if someone finds a workaround in the meantime, we'll be happy to apply it for 3.5.x or 3.6

Comment by Sean McMains [ 09/Apr/08 ]

Here's a patch that seems to work around the issue. If we encounter an error while trying to parse a multipart request, we just have the multipart filter give up and pass the request along unmodified up the filter chain. Since we've seen no other conditions that trigger this exception, it should be a fairly innocuous change.

Comment by Philipp Bracher [ 07/Jul/08 ]

The bug has been fixed in Safari (3.1.2)

Comment by Magnolia International [ 08/Jul/08 ]

--will close with appropriate resolution and fix version (i.e none since we didn't change anything)

Generated at Mon Feb 12 03:33:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.