Agrajag
10-13-2004, 01:21 AM
I've been away for a while and hadn't upgraded to 4.15 (just did). Upon upgrading I was a bit surprised to find that the global User Agent issue is still with us.
Is this planned to be addressed at some point in the near future? For example, www.teevee.org bases your content on the User Agent setting and I personally took the time to sell them on supporting iSilo (which was no small undertaking) which they finally did.
However, due to several other sites failing to work with the default User Agent, it's now forced a choice between which sites I am able to choose from. This clearly is not optimal. In the teevee.org example above, I've gotten them to share a URL for their mobile content but it's not an acceptable solution as they need the User Agent sent each page. Thus, I get a nice, acceptable front page from them and then totally unreadable content for all the other pages.
I don't mean to sound critical. I just thought this was raised as a problem quite a long time ago and assumed it would be resolved by now. Hoping that this is just a misunderstanding on my part and that there's a simple way to address this in 4.15 as it is.
Is this planned to be addressed at some point in the near future? For example, www.teevee.org bases your content on the User Agent setting and I personally took the time to sell them on supporting iSilo (which was no small undertaking) which they finally did.
However, due to several other sites failing to work with the default User Agent, it's now forced a choice between which sites I am able to choose from. This clearly is not optimal. In the teevee.org example above, I've gotten them to share a URL for their mobile content but it's not an acceptable solution as they need the User Agent sent each page. Thus, I get a nice, acceptable front page from them and then totally unreadable content for all the other pages.
I don't mean to sound critical. I just thought this was raised as a problem quite a long time ago and assumed it would be resolved by now. Hoping that this is just a misunderstanding on my part and that there's a simple way to address this in 4.15 as it is.