@joshspicer commented on GitHub:
FWIW the official stance from the golang team is to support two major versions back from the latest (so 1.17, 1.18, and 1.19…
@paolafrancesca commented on GitHub:
Usually its good to require the latest + the previous two minor versions (ie 1.19, 1.18, 1.17)
in order to clarify: my goal is to give users the…
@stefanbenten commented on GitHub:
Usually its good to require the latest + the previous two minor versions (ie 1.19, 1.18, 1.17) and thus setting the minimum to 1.17 would be a good intermediate…
@bahammut commented on GitHub:
and if we upload without run this grep part, how to delete the file without this specific header value !?
@paolafrancesca commented on GitHub:
to shorten the discussion: @joshspicer you should be able to pin to a non-latest version of the azure sdk and still use azure blob storage
is it ok for you?
@toastie89 commented on GitHub:
Hi, the procedure described below works for me: https://github.com/dutchcoders/transfer.sh#x-url-delete https://github.com/dutchcoders/transfer.sh#deleting
Whe…
@stefanbenten commented on GitHub:
You can always reach out via the contact-us form on the website and we'll be happy to help with getting files deleted, if proven ownership of the file exists 👍
@paolafrancesca commented on GitHub:
@bahammut there's no way without knowing the delete token
if you uploaded on transfer.sh you can try asking @stefanbenten
@reorx commented on GitHub:
It's very easy to forget to grep the file because grep is not included in the getting started command.
Would it be a good idea to show the deleted url in upload…
@paolafrancesca commented on GitHub:
@michaelscl do you think the provided solution at infra level is satisfying?
I will look into adding NO_HTTP_AUTH_FROM_WHITELIST in case
@paolafrancesca commented on GitHub:
I think YES, if the implementation is easy.
I was talking about this solution:
have you thought about hosting two instances pointing at the same…
@paolafrancesca commented on GitHub:
@michaelscl as I said my main concern was about complexity of the configuration.
I think a solution migth be to add NO_HTTP_AUTH_FROM_WHITELIST
@michaelscl commented on GitHub:
have you thought about hosting two instances pointing at the same storage, one with and one without upload authentication, and route to the second from the IPs…
@stefanbenten commented on GitHub:
Of course, i understand. That said, i do not know many go projects that do act against the recommendation, especially with regards to security patches, etc.…
@paolafrancesca commented on GitHub:
@joshspicer is this still an issue for you?
Did you add support for azure blob storage?