Following on from the question How to make DownloadOperation from BackgroundDownloader resumable I've got a resumable download working fine locally.
I have completed my webservice and published it as an Azure Website. There appears to be an issue when downloading using HTTPS - when using HTTP the download can be paused and resumed fine and it will carry on, however if I use HTTPS then the download starts again from the start every time I try to resume the download, either from using the Pause and Resume methods or by disabling the internet connection.
I'm connecting to the webservice using the *.azurewebsites.net url which has a valid SSL cert, so I'm not sure why this isn't working.
How do I get resumable background downloads working when using HTTPS?
Related
I am building an application of a live news feed where I used newsfilter.io API. They have a socket server and all you have to do is connect a socket.io client to it. I had the live news feed working perfectly fine and all of a sudden I started getting the error.
NOTE: I am able to have the news feed functioning in INCOGNITO MODE on localhost:3000 but it does not work when on regular browsing localhost: 3000
My code is the same as it was before when the news feed was functioning. I have tried resetting my router several times, cleared cache/cookies, and checked for errors in my code. The application works perfectly fine on incognito but is not working on regular browsing
Proxy error: Could not proxy request /socket.io/?EIO=3&transport=polling&t=NOnTLaS from localhost:3000 to http://127.0.0.1:3001 (ECONNREFUSED).
This is the code that newsfilter.io gives to connect to their server. This code was working perfectly before as stated above but then I started getting network errors. I am using socket.io version 2.0.4 as that is required for this API
I am trying to monitor the requests for images to verify whether the images are loaded from the ios/android cache or they are still being requested from the backend firebase storage. I am using React Native Debugger by enabling Network Inspect but can't seem to observe the requests for images (URIs) of react-native "image" components. How can I monitor the requests for images or how can I check whether the images are loaded from the cache or not?
Thanks!
According to the React Native Debugger documentation here: https://github.com/jhen0409/react-native-debugger/blob/master/docs/network-inspect-of-chrome-devtools.md
It can't inspect request like Images loaded from urls for src, so if
your Image source has a set session, the session can't apply to fetch
and XMLHttpRequest.
The same document refers to Charles & stetho for monitoring these kinds of requests.
If you want to inspect deeper network requests (like requests made
with Image), use tools like Charles or Stetho.
I installed Charles on my mac, installed the certificate on my iOS device, and enabled it using the information contained on the below links. Now I am able to monitor the requests for images.
1- https://www.charlesproxy.com/documentation/getting-started/
2- https://www.donnywals.com/debugging-network-traffic-with-charles/
3- https://www.charlesproxy.com/documentation/using-charles/ssl-certificates/
4- https://stackoverflow.com/a/49129286/1680793
(You may need to visit other linked pages on the links I listed above as needed)
Install Charles on you Mac, launch this help action as described in the documentation I listed:
Charles will guide you about how to install and trust the required certificate on your device:
Some important points:
When you install Charles on your Mac/PC, if it asks for making the
required configurations automatically, allow it.
To install the certificate on your ios device browse to
chls.pro/ssl URL using the SAFARI browser, not Chrome. Then
follow the instructions your device displays to install the
certificate. (I was especially interested in monitoring my iOS device
since android seems to cache the images by default)
If you are using firebase storage as your image store (as I do) and can't see the requests/responses being recorded by Charles, lookout for a message like this: SSL Proxying not enabled for this host. Enable in the Proxy Menu, SSL Proxying Settings
You need to enable SSL proxying for https://firebasestorage.googleapis.com. Add firebasestorage to SSL proxying configuration like so (or whatever URL you are interested in monitoring the communication with):
Charles will be recording everything going on with your mac, to
observe just the "firestore" requests from your app for your images,
use the "filter" box at the bottom of the structure tree on the left
pane (see the first image above).
Don't forget to disable your WIFI proxy after you are done with
Charles or you will not be able to connect to the internet.
Make sure you follow the documentation carefully and pay attention to my list here.
Charles is a paid tool. You can use the trial version for 30 days.
And each launch will terminate itself after 30 mins, so you will need
to restart Charles.
I'm using this library "react-native-af-video-player" for playing videos from my remote server, and its working perfectly on android, but on iOS its giving this error "Oops! there was an error while playing this video please try again later".
I tried giving a random dummy .mp4 url and it worked normally, only the videos from my server are not being read.I added my servers url to the "Exception Domains" in "App Transport Security Settings" in info.plist file but it didn't work. Any help would be appreciated.
Apparently, HTTP servers hosting media files for iOS must support byte-range requests, which iOS uses to perform random access in media playback. (Byte-range support is also known as content-range or partial-range support.) Most, but not all, HTTP 1.1 servers already support byte-range requests.
If you are not sure whether your media server supports byte-range requests, you can open the Terminal application in OS X and use the curl command-line tool to download a short segment from a file on the server:
curl --range 0-99 http://example.com/test.mov -o /dev/null
If the tool reports that it downloaded 100 bytes, the media server correctly handled the byte-range request. If it downloads the entire file, you may need to update the media server to support byte-range requests.
Used auth0 for my react project and it works fine at my local.
When i put my project to the server login page shows up, but after i try to login i get an error.
http://localhost:3000/callback?code=ZSaQ96OshsFfpBUN&state=q3KiPGbEPtIZ3UuSLd.KSbKjdXqk9-pD
firefox says
unable to connect - cant establish a connection to localhost:3000 and on
chrome i got
this site can't be reached - localhost refused to connect
I tried different callback urls on the auth0 side but nothing changed. I do not know exactly what to do actually
It looks like your project isn't running on the same connection that you were locally. Make sure to change all the registered callbacks to their current locations when changing to a different deployment.
When opening some web pages in Safari (iOS - CMS website hosted in a Apache server) it shows the following message.
Tried to remove all scripts from the page and it doesn't worked
Checked Apache access log and none on the requests were logged in access log
Checked Apache error log and no errors are logged
Tried lot of methods to figure it out (technically and logically). Anyone experienced the same issue?
If none of your requests are being logged, then your client isn't getting through and you have a problem outside of your application scope (like a network connectivity or firewall issue)