undefined | Better HN

0 pointstreve9y ago0 comments

I'm doing this with WebDAV too. When I come across a bug that's clearly an implementation problem I weigh how prevalent the software is, how likely they will be able to fix it and if possible I add a user-agent specific workaround so new clients can't rely on the same bug with my server.

0 comments

kr09y ago

But then we add the IE-nightmare of using an accepted user-agent in a new product to workaround cases like this

treveOP9y ago

That nightmare had to do with misbehaving servers. IE had to advertise as Mozilla so servers would serve the better response.

In this case it would be possible for a client to fake a UA, but it's more likely that they weren't aware they were doing things incorrectly and correct the behavior rather than opting in to mimicing a different UA to get the server to behave in a non-standard way.

I haven't seen this happen, and this is one of the most popular DAV implementations. I have seen people fix broken implementations as I've slowly been making the server more strict over the last 10 years.

j / k navigate · click thread line to collapse

0 pointstreve9y ago0 comments

0 comments

kr09y ago

But then we add the IE-nightmare of using an accepted user-agent in a new product to workaround cases like this

treveOP9y ago

That nightmare had to do with misbehaving servers. IE had to advertise as Mozilla so servers would serve the better response.

j / k navigate · click thread line to collapse