-
-
Notifications
You must be signed in to change notification settings - Fork 131
Unconfigured OTR_HTTPPREFIX #399
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
jpmens
added a commit
that referenced
this issue
Aug 12, 2022
I considered having Recorder exit with a fatal diagnostic, but we would break installations which are upgrading and are possibly not interested in Tours. |
jpmens
added a commit
that referenced
this issue
Sep 29, 2022
- FIX: Remove accidental eval (#403) - FIX: Various build fixes (#402) - FIX: now compiles without MQTT (#401) - FIX: read OTR_TOPICS from environment (overrides config); can be overriden by argv - UPD: ocat -v shows compiled-in values, ot-recorder -V runtime ones - FIX: add "OTR_HTTPPREFIX" (verbatim) to tour url if prefix unconfigured (#399) - FIX: Duplicate log entries when running as daemon (#398) - FIX: package build for raspbian
Closing as "slightly fixed". |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If
OTR_HTTPPREFIX
hasn't been configured (via defaults file or environment variable), theurl
saved in a tour view contains a literal(null)
:which results in iOS attempting to use exactly that.
I don't think there's much we can do about it other than slightly "beautify" that null by returning a URL as
as an indication that something needs fixing server-side.
The text was updated successfully, but these errors were encountered: