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
{{ message }}
This repository has been archived by the owner on Oct 11, 2020. It is now read-only.
Server: {picId} et {albumId} are identifiers of raw materials known by server and stored on it.
Client: {password}, {albumPassword} and "my" are only clientside
< title >img.bi - Picture # {{picId}}< /title >
and telling that this is a protected resource with an input area to ask for the missing key. It could let people to give the key by a secure side channel and not in URL. As soon as the key validated, the browser change their location to the full URL with key.
The text was updated successfully, but these errors were encountered:
Just a though: what about an URL redesign to be more open for future updates and more meaningful representation?
Trying to separate what's going on the server and client side:
Server: {picId} et {albumId} are identifiers of raw materials known by server and stored on it.
Client: {password}, {albumPassword} and "my" are only clientside
A GET on https://img.bi/{picId} would return an HTML with:
and telling that this is a protected resource with an input area to ask for the missing key. It could let people to give the key by a secure side channel and not in URL. As soon as the key validated, the browser change their location to the full URL with key.
The text was updated successfully, but these errors were encountered: