As a client developer you have to: 1) follow the spec by ... • Aaron Parecki

Aaron Parecki https://aaronparecki.com/ • Nov 18
I’ll admit it’s a bit of a “hack”. The trick is “aaron@parecki.com” is a URL because if you assume the http scheme then you get http://aaron@parecki.com which is a username but no password with HTTP basic auth. The server can switch what it returns based on that username.

As a client developer you have to: 1) follow the spec by assuming “http” if no scheme is entered, and 2) allow the user-entered URL to contain a username component.

Portland, Oregon • 45°F

Wed, Nov 18, 2020 8:21pm -08:00

5 replies
Have you written a response to this? Let me know the URL:
- Aaron Parecki twitter.com/aaronpk
  
  That's for the final profile URL. The user can enter something different at the start, and if that contains a username component then the trick works.
  
  Thu, Nov 19, 2020 4:25pm +00:00 (via brid-gy.appspot.com)
- Simon Willison twitter.com/simonw
  
  It's a neat trick, what's the correct way of handling it?
  
  Thu, Nov 19, 2020 4:25pm +00:00 (via brid-gy.appspot.com)
- Simon Willison twitter.com/simonw
  
  This seems to contradict the spec - github.com/simonw/dataset…
  
  Thu, Nov 19, 2020 4:24pm +00:00 (via brid-gy.appspot.com)
- Aaron Parecki twitter.com/aaronpk
  
  To be clear, I’m not sure this is a *good* idea, and it also requires a bit of code running at the web server of the root domain, but it does work.
  
  Thu, Nov 19, 2020 4:27am +00:00 (via brid-gy.appspot.com)
- Simon Willison twitter.com/simonw
  
  Thanks, filed an issue github.com/simonw/dataset…
  
  Thu, Nov 19, 2020 4:24am +00:00 (via brid-gy.appspot.com)

Posted in /replies using quill.p3k.io