Andy, On 04 Jun 2013, at 14:42, Sven Van Caekenberghe <[email protected]> wrote:
> On 04 Jun 2013, at 14:13, Sven Van Caekenberghe <[email protected]> wrote: > >> OK: I have a Pharo 2.0 + Seaside 3.1 image with Zn all up to date. What is >> the simplest thing that I can do to trigger the problem ? Can I use one of >> the builtin functional tests ? > > Found it, I broke about every Seaside request ;-) Well, it took longer than expected because my Seaside image contained leftovers from experiments that I long forgot about. Anyway, the following two version should be good: === Name: Zinc-HTTP-SvenVanCaekenberghe.367 Author: SvenVanCaekenberghe Time: 4 June 2013, 4:28:29 am UUID: 04dcc6f1-361f-46c1-a734-746b71460eb2 Ancestors: Zinc-HTTP-SvenVanCaekenberghe.366 Introduction of ZnEntity class>>#matches: to fix ZnEntity class>>#concreteSubclassForType:binary: and ZnEntity>>#contentType: (Thanks Andy Kellens) === Name: Zinc-Seaside-SvenVanCaekenberghe.40 Author: SvenVanCaekenberghe Time: 4 June 2013, 4:24:57 am UUID: a6c5f1db-16b3-46ef-912f-95f54235c518 Ancestors: Zinc-Seaside-SeanDeNigris.39 Modified ZnZincServerAdaptor>>#requestBodyFor: and #requestFieldsFor: to use ZnMimeType>>#matches: after a change in the semantics of ZnMimeType>>#= (mime type parameters like charset are now relevant) (Thx Andy Kellens) === Please confirm that it works for you. Regards, Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org
