Ticket #25 (closed defect: fixed)

Opened 2 years ago

Last modified 23 months ago

No UTF-8 support in friend updates (probably notifications too)

Reported by: me.yahoo.com/a/k59s4tj0xv5vemlieaupj7qasg--#00340 Owned by: me.yahoo.com/lourmoore#b8e34
Priority: critical Milestone: HotBox - Consumer Launch
Component: Friend updates Version:
Keywords: Cc:

Description

charlieville: lou_: fyi, unicode text doesn't show up properly as friend updates
[01:00am] lou_: crap
[01:00am] charlieville: lou_: i get ?'s instead of japanese characters for example

Change History

Changed 2 years ago by https://me.yahoo.com/a/k59s4tj0xv5vemlieaupj7qasg--#00340

  • owner set to https://me.yahoo.com/a/k59s4tj0xv5vemlieaupj7qasg--#00340
  • status changed from new to accepted

Changed 2 years ago by https://me.yahoo.com/a/k59s4tj0xv5vemlieaupj7qasg--#00340

  • status changed from accepted to closed
  • resolution set to fixed

was encoding params again even though shindig already does it.

Changed 2 years ago by https://me.yahoo.com/a/k59s4tj0xv5vemlieaupj7qasg--#00340

  • status changed from closed to reopened
  • resolution deleted

Changed 2 years ago by https://me.yahoo.com/a/k59s4tj0xv5vemlieaupj7qasg--#00340

i don't know what i did but this seems to be magically fixed in my latest build. will leave this issue open for the time-being and verify on sandbox again tomorrow once it's pushed. maybe we picked up a shindig update that fixed this.

Changed 2 years ago by https://me.yahoo.com/a/k59s4tj0xv5vemlieaupj7qasg--#00340

this has again magically ceased to work. I wonder if it's a server level issue. it's possible that sandbox has a bad setup and webvan doesn't, which would bode well for production. need to investigate further.

Changed 2 years ago by https://me.yahoo.com/lourmoore#b8e34

  • owner changed from https://me.yahoo.com/a/k59s4tj0xv5vemlieaupj7qasg--#00340 to https://me.yahoo.com/lourmoore#b8e34
  • status changed from reopened to accepted

Changed 2 years ago by https://me.yahoo.com/lourmoore#b8e34

We now know the problem -- api servers use tomcat 6 which doesn't have the double-encoding issues that resin 2.x has. We can "fix" this by adding a handler that double-decodes the data in the same messed up way resin does.

Changed 23 months ago by https://me.yahoo.com/a/47gas9sa15zba1y9rwezhrxjpfox#5d2e4

  • status changed from accepted to closed
  • resolution set to fixed

Added "change utf-8 to latin-1" on api side to accomodate for resin issue

Note: See TracTickets for help on using tickets.
Close