You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of requiring an update server to respond with a specific JSON schema, what if we also allowed a server to respond with an HTTP 301, 302, 303 or 307 redirect pointing to the new release URL? This would allow for third-party distribution services, such as my own to be more easily integrated with Squirrel, without the third-party service needing to add a compatibility layer for Squirrel.Mac (i.e. at minimum, a top-level url property in the response payload.)
Since this would be in addition to the 200 JSON response, this should be a backwards-compatible change.
What do you all think?
p.s. I'd love to sponsor this/donate to Squirrel on behalf of Keygen. Let me know if you provide options for that, or if somebody else wants to jump in with approval from the maintainers. 🙂
The text was updated successfully, but these errors were encountered:
Given that this is 20 years old well established web tech, I thought this would Just Work (tm.)
And now I'm forced to come up with some terrible rewrite rule to make this happen.
Please implement this!
Instead of requiring an update server to respond with a specific JSON schema, what if we also allowed a server to respond with an HTTP
301
,302
,303
or307
redirect pointing to the new release URL? This would allow for third-party distribution services, such as my own to be more easily integrated with Squirrel, without the third-party service needing to add a compatibility layer for Squirrel.Mac (i.e. at minimum, a top-levelurl
property in the response payload.)Since this would be in addition to the
200
JSON response, this should be a backwards-compatible change.What do you all think?
p.s. I'd love to sponsor this/donate to Squirrel on behalf of Keygen. Let me know if you provide options for that, or if somebody else wants to jump in with approval from the maintainers. 🙂
The text was updated successfully, but these errors were encountered: