Android Question [Solved]HttpJob

[Ale_resource]

Hi I should download a json from a web service via an api call ,This is the code I used :

    Dim JobDoc As HttpJob
    JobDoc.Initialize("JobDoc",Me)
    JobDoc.Download("https://webapide.aliasgrouplab.it/api/DocumentoAttivo/100009")
    JobDoc.GetRequest.SetHeader("APIKey","2b6dedd8efc2668b56b2d070424a436f0027134c293199724ee80.........")
    JobDoc.GetRequest.SetHeader("APISecret","47c55ace70212b27d79db9e5824d09541ea120de3e88bf8993c4152c62239b0df9382242e9570dd00e6cfcf3980ba74a95630305cf00661fe89d8......."")
    JobDoc.GetRequest.SetHeader("CodiceCliente","0185469.....")
    Wait For (JobDoc) JobDone(JobDoc As HttpJob)
    If JobDoc.Success Then
        Log(JobDoc.GetString)
    Else
        Log(JobDoc.ErrorMessage)
    End If

and this is the documentation :

but i can't download anything, i always get this error

I tried with Postman to manage the api and it works fine.
What am I doing wrong ?

 

[Ale_resource]

how did you solve it? @mcqueccu

 

[mcqueccu]

how did you solve it? @mcqueccu

Its not solved yet. It worked briefly I realised it worked because of something. Am still debugging and will bring the result out

 

[mcqueccu]

Its not solved yet. It worked briefly I realised it worked because of something. Am still debugging and will bring the result out

I tried the code in B4J, using jOKhttputils2. The code ONLY works if these two things are done.

1. Add Conditional symbol (HU2_ACCEPTALL) to the build configurations and
2. When a software called HTTP debugger is opened (https://www.httpdebugger.com/)

So, when the http dubugger software on the machine is closed, it gives 401, but when its opened and running, I get 200 response>

There may be something either in the okhttputils or the API not right

 

[Ale_resource]

Hello, I understand the problem. Practically the library sends the Headers all in lowercase for example APISecret is sent as apisecret and on the server side they are case sensitive.

 

[mc73]

Hello, I understand the problem. Practically the library sends the Headers all in lowercase for example APISecret is sent as apisecret and on the server side they are case sensitive.

Then I think this is a problem with the API since to my knowledge, header names are case insensitive.

 

[Andrew (Digitwell)]

Just tried the case sensitivity in Postman. Yes, it looks like the APIKey header needs to be the exact case given. The other 2 are fine.

This works:

This does not:

 

[Ale_resource]

The programmer told me that are casesensitive and cannot change , so how can I fix it?

 

[Andrew (Digitwell)]

I don't think there is an easy solution to this from B4x side.

Looking at the source for okHttp on git hub.

B4A/Libs_OkHttp/src/anywheresoftware/b4h/okhttp/OkHttpClientWrapper.java at master · AnywhereSoftware/B4A

B4A core libraries. Contribute to AnywhereSoftware/B4A development by creating an account on GitHub.

github.com

there is the following:

/**
         * Sets the value of the header with the given name. If no such header exists then a new header will be added.
         */
        public void SetHeader(String Name, String Value) {
            builder.addHeader(Name, Value);
        }

So if I have read this correctly it seems to be the base HttpRequest java code which is lowercasing the header value. As the value given is just passed without change.

The developer should really change their API to be correct. The only other solution I can see is to use something as a buffer which can make case sensitive calls.
It may be possible to inject some javascript into a webview or use PHP on a server.

 

[Ale_resource]

is there a way to "work around" this problem? or should the library be corrected?

 

[mc73]

The programmer told me that are casesensitive and cannot change , so how can I fix it?

Then they are not following the rule. Sooner or later they'll have to adjust to that, so why not now?
In the mean time, if the old httpUtils works, I would go with that.

 

[mcqueccu]

(B4A-B4J Chargeable) Amir_Retrofit

Type-safe HTTP client for Android and Java by Square, Inc. The best android library for HTTP client. Easier and faster !? Amir_Retrofit (including rxJava) Amir_RetroMin (Simple Version of Amir_Retrofit, just use it for simple apps) jAmir_Retrofit (B4J) Some of the Retrofit features ...

www.b4x.com

 

[OliverA]

Hello, I understand the problem. Practically the library sends the Headers all in lowercase for example APISecret is sent as apisecret and on the server side they are case sensitive

Are you sure. Now, I'm using B4J to test this, but I'm having the same issues with OP's site. Here is the Wireshark capture for a request created in B4J to PTSV2

G 4.·NáEÌ´@À¨Øï"õcPccÚ¾hP¿GET /t/****not publishing this part ****/post HTTP/1.1
APIKey: ce8ac27ca1c73f5afd1d2f66976aa6be88335fe6e282a921acc963d575163b6e
APISecret: e290984a3d0d8ae286306dc152b5493c70b637ffcc48f2049ba90cab73f3e26c337fa2fc97379ce9b52586b98ae92c3934bf261731d095a949a47fbb2853f58b
CodiceCliente: 01854690433
Content-Length: 0
Cache-Control: no-cache
Host: ptsv2.com
Connection: Keep-Alive
Accept-Encoding: gzip
User-Agent: okhttp/3.12.12

As you can see, no lowercasing was performed by the okhttp3 library

 

[Andrew (Digitwell)]

Interesting. All I can say is that in my tests with PostMan changing the "APIKey" header to "APIkey" causes the 401 error.
Making APISecret and CodiceCliente lowercase or original case has no effect - the call still works until a change to APIKey is made.

 

[Ale_resource]

Are you sure. Now, I'm using B4J to test this, but I'm having the same issues with OP's site. Here is the Wireshark capture for a request created in B4J to PTSV2

As you can see, no lowercasing was performed by the okhttp3 library

yes, i'm sure .. i was also confirmed by the programmer who created the API that there is a casesensitive check on the apikey header

 

[OliverA]

casesensitive check on the apikey header

That’s an issue with the API and the developer, since by standard headers are case insensitive

RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1

HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol referred to as "HTTP/1.1", and is an update to RFC 2068. [STANDARDS-TRACK]

datatracker.ietf.org

 

[Ale_resource]

That’s an issue with the API and the developer, since by standard headers are case insensitive

RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1

HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol referred to as "HTTP/1.1", and is an update to RFC 2068. [STANDARDS-TRACK]

datatracker.ietf.org

yes I know, that's what I told the programmer .. who replied that no one has ever had problems and so I have to adapt

 

[OliverA]

who replied that no one has ever had problems and so I have to adapt

What I don’t get is why wireshark shows that the case is not changed, yet access still does not work. Almost like it is an issue on his side