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. > > casServiceValidationFailure.jsp contains: > > <%@ page session="false" contentType="text/plain" %> > > casServiceValidationSuccess.jsp contains: > > <%@ page session="false" %> > > I don't see reference to content type in http://www.jasig.org/cas/protocol, > and don't see anything I can use for guidance in the 4.0 snapshot I have. > It doesn't look intentional that I can see. > > What should it be? text/xml, application/xml, text/plain, ...? > > Thanks. > Tom. > -- > 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 > > -- 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
