Timeline for URL shortener using Flask
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 25, 2024 at 21:53 | comment | added | J_H | @BeeH. yeah, I think I agree with you that Author failed to convey a technical idea, or that in my (frequent!) foolishness and fallibility I failed to grasp the idea. This comes back to the frequent interchange / ambiguity in this codebase between full and relative URLs when we see "url" mentioned. Given the observed diversity of interpretations so far imposed, it suggests that being more rigorous and explicit about use of the term would, in future months, be a boon to maintenance engineers. I have grown accustomed in various codebases to seeing BASE_URL + foo, which dispels ambiguity. | |
| Mar 25, 2024 at 20:49 | comment | added | Bee H. |
Your critique "loss of protocol" incorrect/misguided. The request.host is @booboo's host name. So if I pass in the URL https://google.com/search?q=the-answer-to-life-the-universe-everything, the returned shortened_url would look something like https://booboo.com/a3bf1c
|
|
| Mar 25, 2024 at 15:48 | history | edited | J_H | CC BY-SA 4.0 |
added 345 characters in body
|
| Mar 25, 2024 at 15:37 | history | edited | J_H | CC BY-SA 4.0 |
Kerckhoffs's principle
|
| Mar 25, 2024 at 15:30 | history | edited | J_H | CC BY-SA 4.0 |
edited body
|
| Mar 25, 2024 at 15:23 | history | answered | J_H | CC BY-SA 4.0 |