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
Is there a reason you're not using the http scheme in the api uri? The current endpoints the gem supports seem to support https. Is it because future endpoints might not support https?
The text was updated successfully, but these errors were encountered:
I feel like if you want to save a few processor cycles in exchange for less security, you'd want to keep the http scheme around. Especially, say, if you're making a ton of Awe.sm requests. Making https optional would be prudent here, IMO.
Oh, and to be clear, neither I nor my co-maintainer are in any way officially connected with Awe.sm, so we have no idea whether the https endpoint will have continued support or not. (It sounded like you might think that based on the last question you asked.)
Is there a reason you're not using the http scheme in the api uri? The current endpoints the gem supports seem to support https. Is it because future endpoints might not support https?
The text was updated successfully, but these errors were encountered: