I can file an enhancement request, but it'd be good to know if any (common) clients explicitly look for specific MIME types, such as text/plain.
I'd expect/hope most (modern) application servers to serve UTF-8 by default. Explicitly specifying charset in the JSPs might then be considered deprecated. On the other hand, explicitly stating charset could be considered good 'defensive' programming. :-) Thanks. Tom. On Sep 19, 2013, at 1:22 AM, Jérôme LELEU <[email protected]> wrote: > Hi, > > You raise a good question. The real content is XML. We can also wonder why > there isn't any encoding defined (should be UTF-8). > So I guess it could be : contentType="text/xml; charset=UTF-8" for both JSPs. > I don't know if there is some legacy reason here. > Best regards, > Jérôme > > 2013/9/19 Tom Poage <[email protected]> > One of our users noticed that Content-type in the HTTP header for a > serviceValidate error is text/plain, while that for a serviceValidate success > is text/html. The former will display the 'raw' XML in a browser, the latter > will not. They found it confusing. -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
