Received 401 Unauthorized response with REST request
Publication date: August 8, 2018
I am trying to fetch all form records using the documented pattern ‘/apps/APP_ID/dtypes/entity/ENTITY_ID.json’ in Java 8, with Retrofit2, and Gson to handle JSON stuff, but I received 401 response no matter how I try.
The complete URL can produce valid response in Chrome browser, but receives only brackets() in Safari.
I tried to set an API key in the body, but the Retrofit framework complained that body is not acceptable in a GET method. That seems to violate the specifications of HTTP 1.1.
Then I tried to use POST method instead, got the same 401 response.
I have no idea. Is there any operational sample written in Java?
Unable to download charts
Publication date: August 13, 2018
I’m sure there is a simple solution. Recently I installed an ssl certififcate for my website where I embed charts. But now when I go to download the charts I am unable to. Can you solve this?
Mobile Friendly pages
Publication date: August 16, 2018
I am using your login query page as a landing page for one of my mobile app functions but the URL for the login query appears way too small (tiny) on the apps browser and even my mobile device’s browser. Can all of your pages be made mobile friendly please?
Publication date: September 17, 2018
Can you help with this please. I have a acquired a new computer that I am keeping as virgin so that I can test applications. One issue that I have with my Record View html content is that IE8 and 9 display the Mixed Content message – which the only solution I know is to change the browser security settings. However, I note that on the QuintaDB web site your own examples do not have this message displayed in your demo databases.
I can see that my using my own html content I have replaced what could be the calls to prevent this, here is a paste from one your demo sites;
Should I be using a similar head content in my html? If so, what are the defaults?
The links are called within a Record View html directly from QuintaDB url fields. The only exception is a Mail to link calling an QuintaDB email link. There are no other links than within the QuintaDB database record. Here is a test page url;
It seems that if QuintaDB calls Record View then the fact that it uses https and other links in the database are normal http that IE (fine in Firefox and Google Chrome) wants the user to respond to a badly phrased security message. For the time being I will insert a help link on the pages to explain the issue but we really should have a better work around that this. Is it possible for QuintaDB to either detect the existence of http calls and then use http to access Record View? Or is there some way that Record View be parameter set by the developer/user to use http?
I know and understand this is not an issue of your making, however if users are to feature url links in their database and call these from Record View then QuintaDB should be able to facilitate this without having web site visitors be potentially frightened away from applications by a Microsoft message.
Iframe in IE and not only
Publication date: August 16, 2018
I am using an IFrame for the database via Firefox, Google Chrome or Safari it looks as it should relative to integration.
However, when you look at through Internet Explorer it has a white box around it. When changing the background image on mytaskhelper it makes the “translucent” look of the embedded IFrame whatever color that is on all of the browsers and not just IE. Also, when viewing the IFrame via IE7, you cannot see the cursor when attempting to enter into the fields to put information.