Some problems you may have, that we know of:
We use two different date formats:
1) The "European" date format (DD.MM.YYYY) with a point as delimiter.
2) The date format according to ISO 8601 (YYYY-MM-DD) with a dash as delimiter.
We are not using the "US" date format (MM/DD/YYYY). All dates are CET.
Requests without User-Agent may not be accepted by the server. In these cases error "406 not acceptable" will occur. The User-Agent should give a inference to your company (e.g. company xy, customer xy). Don't use a User-Agent String of a common browser.
A HTTP-Request needs at least the following:
GET /~apgmontagne/?type=rawdate&id=[ID]&report=[REPORT]&ref=[TOKEN] HTTP/1.1 Host: www.infosnow.ch User-Agent: Your User Agent StringFor more details read the HTTP 1.1 specification:
The User-Agent request-header field contains information about the user agent originating the request. This is for statistical purposes, the tracing of protocol violations, and automated recognition of user agents for the sake of tailoring responses to avoid particular user agent limitations. User agents SHOULD include this field with requests. The field can contain multiple product tokens (section 3.8) and comments identifying the agent and any subproducts which form a significant part of the user agent. By convention, the product tokens are listed in order of their significance for identifying the application.
User-Agent = "User-Agent" ":" 1*( product | comment ) Example: User-Agent: CERN-LineMode/2.15 libwww/2.17b3
A CDATA-Section contains plain text with non-printable characters <CR><LF> as linefeed. It is up to you to encode such text if needed.
<DataTag><![CDATA[ ... DATA ... ... DATA ... ]]></DataTag>If you want text to be shown with proper linefeeds on HTML-Pages, you need to replace the linefeeds with the Tag <BR>. Depending on your tech portfolio, you could do this with something as simple as:
MenuMyString.replace("\n","<br>");