<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: OnCommand API Services Web UI character encoding error in Software Development Kit (SDK) and API Discussions</title>
    <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/OnCommand-API-Services-Web-UI-character-encoding-error/m-p/119181#M1918</link>
    <description>&lt;P&gt;Pl. open oncommand API Services Web UI using https.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;example:&lt;/P&gt;&lt;P&gt;https://&amp;lt;IP-ADDRESS&amp;gt;/api-admin/#/login&lt;/P&gt;</description>
    <pubDate>Wed, 11 May 2016 09:10:21 GMT</pubDate>
    <dc:creator>pukale</dc:creator>
    <dc:date>2016-05-11T09:10:21Z</dc:date>
    <item>
      <title>OnCommand API Services Web UI character encoding error</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/OnCommand-API-Services-Web-UI-character-encoding-error/m-p/118099#M1899</link>
      <description>&lt;P&gt;I'm trying to setup an OnCommand Services API machine on CentOS 7.0.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I try to access the Web UI, I get the following error:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature.&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Maybe someone can point me in the right direction.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;edit:&lt;/P&gt;&lt;P&gt;the solution is simple: You must use HTTPS and not HTTP, because there is no redirect.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 21:28:58 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/OnCommand-API-Services-Web-UI-character-encoding-error/m-p/118099#M1899</guid>
      <dc:creator>acjackson</dc:creator>
      <dc:date>2025-06-04T21:28:58Z</dc:date>
    </item>
    <item>
      <title>Re: OnCommand API Services Web UI character encoding error</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/OnCommand-API-Services-Web-UI-character-encoding-error/m-p/119181#M1918</link>
      <description>&lt;P&gt;Pl. open oncommand API Services Web UI using https.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;example:&lt;/P&gt;&lt;P&gt;https://&amp;lt;IP-ADDRESS&amp;gt;/api-admin/#/login&lt;/P&gt;</description>
      <pubDate>Wed, 11 May 2016 09:10:21 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/OnCommand-API-Services-Web-UI-character-encoding-error/m-p/119181#M1918</guid>
      <dc:creator>pukale</dc:creator>
      <dc:date>2016-05-11T09:10:21Z</dc:date>
    </item>
  </channel>
</rss>

