Forum Replies Created
-
AuthorPosts
-
May 9, 2021 at 5:28 am in reply to: iOS app version 2.2.2 possibly losing saved sites on update #70047
bensweetParticipantConfirming the app has been working well. Looks like the basic auth was actually an issue with CORS. Somewhere in all of this (I haven’t looked too far in the iOS updates) it looks as though something has changed with the CORS preflight request and the Apache reverse proxy started to fail CORS on a number of fronts.
For what its worth I always had Header set Access-Control-Allow-Origin “*” which for year had worked ok but the preflight was killing this. Had to make several changes to get this to work, as below
# Enable CORS
Header unset Access-Control-Allow-Origin
Header always set Access-Control-Allow-Origin “*”
Header always set Access-Control-Allow-Methods “POST, GET, OPTIONS, DELETE, PUT”
Header always set Access-Control-Allow-Headers “append,delete,entries,foreach,get,has,keys,set,values,Authorization”# Rewrite OPTIONS message to return Http ok message
RewriteEngine On
RewriteCond %{REQUEST_METHOD} OPTIONS
RewriteRule ^(.*)$ $1 [R=200,L]April 11, 2021 at 11:11 pm in reply to: iOS app version 2.2.2 possibly losing saved sites on update #69747
bensweetParticipantRay, 2.2.4 on my iPhone. Seems that it is something with basic auth that is broken. My reverse proxy only requires basic auth if traffic is routed via the WAN otherwise no auth is required in Apache. If iOS is on the LAN, app works with a signed SSL certificate without basic auth. If iOS is on the WAN, even with basic auth then setup in the app it doesn’t work. Doing the same on Android with 2.2.4 works as expected with SSL + basic auth.
Is there something that has changed in the latest iOS software that isn’t specific to the app – O/S or SDK?
April 10, 2021 at 4:03 pm in reply to: iOS app version 2.2.2 possibly losing saved sites on update #69734
bensweetParticipantThere looks like something else is still going on. I have 2x sprinklers in different setups, neither works on the IOS app using a remote connection (http / https + reverse proxy + basic auth) but both work on a local connection (http + reverse proxy, no basic auth). I recently updated my phone to iOS14.4.2.
When setting up in the app a new connection to the https + reverse proxy + basic auth ospi system it reasonably quickly returns Check IP/Port then try again. When doing the same for the http + reverse proxy + basic auth ospi system it times out after about 40sec
For both systems if I take the connection path entered into the app and test in a web browser in iOS, once I get past the basic auth they work fine. App broke some time in the last week for me.
bensweetParticipantHas any progress been made in the weather service space since DarkSky could (and probably will) be turned off at the end of the year?
I took another look at OpenWeatherMap and their API data but for me it was still very inaccurate compared the DarkSky or other weather services – for Australian weather.
Interested to see that OWM now have a free plan similar to what WU used to have, from memory they were missing historical data previously with their free plan?
There are a few others – Climacell, Visualcrossing? -
AuthorPosts