Forward Signed Date with airSlate SignNow

Forward signed date

so yesterday I shared a performance experiment in which I started cashing cryptographically signed URLs in Redis and after I posted that it occurred to me that I don't think I've ever talked about my strategies for generating cash friendly or CDN friendly sign URLs and the way my strategy works is by bucketing the expiration date of a signed URL so I might bucket based on month which means that any sign URL for a particular resource that's generated within a given month uses a consistent expiration date such that the generated signed URL is the same within a month for a particular resource so for example given a date here which will default to the current timestamp in order to generate an expiration date for a sign URL I would create a date that is the first of the current month right so it's August 21st right now so this would become August first and then I roll forward one month to get the expiration date so the expiration date for a URL generated on August 21st would become September first right it's the first day of the following month and to look at how this works we can create a simple loop here where I start on August first and I'm gonna loop 50 days right and for each iteration that loop I'm just gonna add a date to that first date and then I'm gonna get the monthly bucket for the particular date and I'm gonna output it and if we run this code what we can see here is that on August first we start generating expiration dates for September first so it's the end of that rolling month and then any expiration date generated during the month of August always results in a September first expiration right including up to August 31st which also has a September for the expiration and then the second we roll into September you can see that our expiration dates roll forward another month too October 1st now from an in application experience this is totally fine you know we'll get to the end of this bucket and then subsequent URLs will start generating new signed URLs using the following months expiration now again from an in application standpoint this is great because an application experience has the luxury of making subsequent requests to the application and generating new URLs that then get rendered within the application but the problem is not all signed URLs are consumed directly within the application oftentimes we will use a sign URL in an external context like an email so using this strategy let's say I send out an email on August 31st it has an embedded image that has an expiration date of September first now the next day the user comes in opens that email and suddenly that URL that was generated just maybe hours before is no longer valid by the time the user opens that email and they're presented...