|
From: <tr...@do...> - 2013-09-12 22:22:33
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Form URL Encoded POSTs should explicitly state UTF-8 charset where appropriate</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>1.0.1</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Storage</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>High</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Bug</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Reported by Matthias Schwalbe on the bugs list - <a href="http://sourceforge.net/p/dotnetrdf/mailman/message/31394185/">http://sourceforge.net/p/dotnetrdf/mailman/message/31394185/</a></p>
<p>
When we POST form URL encoded content we are often posting UTF-8 content and the default character set for form URL encoded is ISO-8859-1 (Latin 1) which can cause encoding issues on the receiving end. Thus wherever appropriate code needs to explicitly state the character set for form URL encoded content in the Content-Type header.</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=374" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=374</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|