So let's see. They do UA detection on the server side delivering different content depending on the UA. In their HTTP request, there is a: X-Powered-By: An awesome IT Team: Apply now and help to shape the technical future of the world's largest online hotel search. And in the HTML <!-- Want to get paid to dissect our code? We're hiring developers: www.trivago.com/jobs --> Let's help them shape a larger mobile landscape. Pun intended ;) That would be nice if someone from their team could help us fix it. They send → http -b http://www.trivago.sg/ 'User-Agent:Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0' > fxos.txt → http -b http://www.trivago.sg/ 'User-Agent:Mozilla/5.0 (Android; Mobile; rv:36.0) Gecko/36.0 Firefox/36.0' > fxand.txt → ls -al 386122 17 mar 15:04 fxand.txt 184697 17 mar 15:03 fxos.txt To note that the HTML sent to desktop is lighter than the Android version (without counting the assets). The content sent to Firefox for Android works the same. So it's just a matter of wrong detection. The Firefox OS UA is Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0 (version numbers are not relevant) Next step: They need to be contacted. All the open positions for IT are in Dusseldorf and Leipzig in Germany. They also have a contact form http://www.trivago.com/static/contact_us/contact_us And they are on https://github.com/trivago
Whiteboard: [country-sg] → [country-sg] [serversniff] [contactready]
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.