[Building Sakai] BLTI : BaseString generation

[Matthew Jones]

Nevermind, that's just another error I get when "Open in a New Window" is
checked with a site using that title.

I also get a blank page when Debug Launch is selected.

The URIEncoding looks okay.

On Wed, Oct 10, 2012 at 6:35 PM, Yegeneswari Nagappan
<ynagappan at unicon.net>wrote:

> Hi Matthew,
>
> I don't see such an exception on my local. Not sure why you get that
> error. If its not already set, you can try configuring tomcat and set
> URIEncoding to "UTF-8" and check if that fixes the issue.
>
> Thanks
> Esh
> ----- Original Message -----
> From: "Matthew Jones" <matthew at longsight.com>
> To: "Yegeneswari Nagappan" <ynagappan at unicon.net>
> Cc: "Sakai-Dev" <sakai-dev at collab.sakaiproject.org>, csev at umich.edu
> Sent: Wednesday, October 10, 2012 3:00:00 PM
> Subject: Re: [Building Sakai] BLTI : BaseString generation
>
> For me in Sakai a site with this title is throwing an exception.
>
> 2012-10-10 17:53:08,250 INFO http-bio-8080-exec-49
> org.sakaiproject.linktool.LinkToolUtil - LinkToolSetup complete
> java.io.CharConversionException: Not an ISO 8859-1 character: ’
> at javax.servlet.ServletOutputStream.print(ServletOutputStream.java:77)
> at javax.servlet.ServletOutputStream.println(ServletOutputStream.java:187)
> at
> org.sakaiproject.basiclti.impl.BasicLTISecurityServiceImpl.sendHTMLPage(BasicLTISecurityServiceImpl.java:222)
> at
> org.sakaiproject.basiclti.impl.BasicLTISecurityServiceImpl.access$200(BasicLTISecurityServiceImpl.java:71)
> at
> org.sakaiproject.basiclti.impl.BasicLTISecurityServiceImpl$1.handleAccess(BasicLTISecurityServiceImpl.java:322)
>
>
> On Wed, Oct 10, 2012 at 5:35 PM, Yegeneswari Nagappan <
> ynagappan at unicon.net > wrote:
>
>
> Hi,
>
> We are using BLTI tool in Sakai 2.9 and need some clarification on how the
> BaseString is generated for parameters with special characters in it. The
> launch from a site with title "French d’économie" (has accent character in
> title)failed because the BaseString that got generated for the title on
> Sakai is different from the value on the BLTI Producer system.
>
> Should the string be utf-8 encoded character set prior to Step 1 mentioned
> in OAuth 1.0 Spec for Percent-encoding strings (
> http://tools.ietf.org/html/rfc5849#section-3.6 ) ?
>
> On Sakai side, the string "French d’économie" was used directly in Step 1
> where as on the BLTI producer system, the utf-8 encoded character set i.e
> "French d’économie" was used in Step 1.
>
> Can you please confirm if Sakai is implemented as per spec.
>
> Thanks for your help!
>
> --
> Esh
> P.S :I used this site http://coderstoolbox.net/string/ to find the utf-8
> encoded character set for given string.
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20121010/92ffa7d1/attachment.html