|
|
|
Rank: Starting Member
Groups: Registered
Joined: 3/11/2005
Posts: 3
Location: ,
|
Hello,
According to the Java sample regarding IPN, the following line:
str = str + "&" + paramName + "=" + URLEncoder.encode(paramValue);
The URLEncoder.encode() used above is a depricated function. Now I've used "UTF-8" as a second parameter. But we received an error "INVALID"
when I post the reply back to the IPN server.
I received a first_name to our system as "Jurri<EB>n" and I think this is why the IPN failed (response was "INVALID").
Could it be PayPal uses another charset encoding to read/validate our
response?
What charset does the PayPal system use?
How can I validate that invalid request wasn't caused by our system?
Bye,
Jeroen van der Grift.
Software Developer with First8 B.V.
|
|
|
|
|
|
|
|
|
Rank: Starting Member
Groups: Registered
Joined: 2/18/2004
Posts: 48
Location: ,
|
Hi jeroeng,
I just noticed the same problem myself. item_name and other fields related to the transaction seem to be encoded in UTF-8, but other fields like first_name and last_name are not, even when you pass in UTF-8 as your encoding for Web Accept buttons.
I think you might have uncovered a bug in PayPal, as it's clearly not intended behavior. Hopefully they will address this issue.
As far as the encoding used for first names/last names, it seems like it's currently Windows-1252 (or ISO 8859-1).
|
|
|
|
Rank: Starting Member
Groups: Registered
Joined: 3/11/2005
Posts: 3
Location: ,
|
Any idea how to contact the PayPal developer team? Or do I need to wait till they put a response on this forum?
|
|
|
|
Rank: Starting Member
Groups: Registered
Joined: 10/17/2002
Posts: 2,139
Location: ,
|
Hello, You can use the web form in the help section of Developer Central or click on the handle of my name to send off an email. We are aware of this issue and we are working to resolve it, I will post an update to this topic when I have addtional information or a resolution. Stephen Ivaskevicius PayPal/eBay, Inc. www.paypal.com/pdn
|
|
|
|
Rank: Starting Member
Groups: Registered
Joined: 3/17/2005
Posts: 4
Location: ,
|
I contacted PayPal regarding this issue but they just keep pointing me to the PDN. Hopefully they will address the issue soon. Steve Perrins SCP Computer Services Kind regards, Steve Perrins http://www.scp-computers.co.uk
|
|
|
|
Rank: Starting Member
Groups: Registered
Joined: 10/17/2002
Posts: 2,139
Location: ,
|
Hello, The characters are changed in the IPN post when using the language Encoding in your profile of Western European Languages. This is passed as the 'form_charet' with a value of 'windows-1252'. Example: ä = %E4 ö = %F6 ü = %FC Ä = %C4 Ö = %D6 Ü = %DC ß = %DF Stephen Ivaskevicius PayPal/eBay, Inc. www.paypal.com/pdn
|
|
|
|
Rank: Starting Member
Groups: Registered
Joined: 6/14/2004
Posts: 8
Location: ,
|
The majority of our IPNs are VERIFIED with the "windows-1252" charset, including the ü, ß, etc.
However, from time to time, we got some INVALID IPNs, which is found valid when checked through the Paypal website.
We suspect that some characters, e.g. the euro sign, is not working with the charset...
How could we eliminate these rare cases?
We're currently running on W2k. And is going to migrate to RedHat soon.
|
|
|
|
Rank: Starting Member
Groups: Registered
Joined: 3/11/2005
Posts: 3
Location: ,
|
yesterday we received an INVALID response. This time the item_name field contained some "weird" data:
PayPal IPN: item_name= ...(560<E2><82><AC> + 10<E2><82><AC> ...)
where de ... is normally readable but removed for privacy reasons.
Can someone please verify if this indeed is an error at PayPal's side? We are sending everything in the "windows-1252" format.
Thanks!
Jeroen.
|
|
|
|
Guest (2)
|
YAFVision Theme by Jaben Cargman (Tiny Gecko)Powered by YAF |
YAF © 2003-2009, Yet Another Forum.NETThis page was generated in 0.359 seconds.
