Using an API endpoint as a connectivity URL about connectivity HOT 7 CLOSED

Ah thats brilliant, thanks!

from connectivity.

The current implementation only checks that the word 'Success' is returned in the response so that would work.

I meant to get around to writing a more robust implementation of this check just in case it ever turns out to be the case that captive portal happens to contain the word as part of the web page served however I'll ensure that I introduce this in a backwards-compatible manner when I do. Hope this helps!

from connectivity.

I've added the option to customise the validity test used when checking connectivity URLs. To only check that the response contains the word Success you can set the following:

connectivity.expectedResponseString = "Success" // this is the default value
connectivity.validationMode = .containsExpectedResponseString

from connectivity.

Hey @rwbutler, is there any way of being able to set an authorization header token for a connectivity URL? I have an API endpoint thats protected using JWT tokens. Currently have to run a separate unprotected route for checking connectivity status - just wondering if there's an easy way around this, as it would be good to allow only authorised clients to access the endpoint.

from connectivity.

I haven’t got a way of doing this just yet but I’ll look into it and get back to you 👍🏻

_{Sent with GitHawk}

from connectivity.

@vin047 I've just released v2.2.0 which includes a bearerToken property. If you set your JWT token here it should be supplied to your endpoint. Hope this helps.

from connectivity.

Hey, sorry for the delay in getting back to you. I just had a chance to implement version 2.2.0 and can confirm the bearerToken feature works as expected. Thanks a lot for the effort and for this library! 👍 🥇

from connectivity.