-
Notifications
You must be signed in to change notification settings - Fork 252
UTF-8 encoding fix. #44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I believe I'm having this same issue in my application:
I'll try your fix and let you know if it works for me. Update: It worked, great fix! (+1) I'm still pretty new to Ruby so I can't say for sure whether or not what you did is the best way to fix the problem, but your commit definitely does the job. This bug was basically making net-ldap unusable for me, so I think it would be a good idea to pull this commit ASAP. |
I second that, we have the same issues with Microsoft products and would be grateful for a fix. |
This solves also our problems with Microsoft products. Please merge this, so we can use this without manual patching. |
I finally gave up waiting for this bug fix and just installed the net-ldap-1 gem, instead. Works like a charm. How about keeping the official branch up-to-date please. |
Merged all the back pull requests and I'll push out a 0.4 tonight Rory O'Connell On Tuesday, August 28, 2012 at 12:08 PM, Doug Hall wrote:
|
Uh, no 0.4? This was 20 days ago... |
@RoryO - I was bit by this bug too. Was wondering if you could push out the 0.4 soon? Thanks! |
Would like to see a new release for this too. Cheers. |
Agreed here! |
A new release would be fine. The utf-8 bug is very annoying. |
Not sure if it's the best way to fix the problem, but at least it makes net-ldap usable for me. |
Just stumbled upon this bug while setting up Redmine... New release would be highly appreciated ;( |
I got that code update manually into my local gem lib. So now instead of of error I get nil returned :
|
+1 for a new release. This is really annoying. |
Why is this still not pulled? |
The issue itself should be fixed in the current master branch (at least I didn't experience any issues with it) and you can reference it via your Gemfile like this: gem "net-ldap", :git => "git://github.com/ruby-ldap/ruby-net-ldap.git", :branch => "master" But it would be nice if the gem on rubygems.org would have been updated. Sadly this project seems a bit abandoned. |
Weird; if it was merged with master, Github should say so. Thanks anyway. |
As you can see on https://github.com/ruby-ldap/ruby-net-ldap/commits/master/lib/net/ber/core_ext/string.rb there already was some code merging which should have fixed this issue. So normally this pull request here could be closed. The issue really is that the gem hasn't been updated and people are thus coming to this repo to complain about code issues for whom fixes already could and should have been "shipped". |
It looks like this pull request is a duplicate of #41, which was pulled and is now closed. Not exactly the same code change, but solves the same problem. |
|
I am out of the office until 11.02.2013.Meine E-Mails werden nicht gelesen oder weitergeleitet.Gerne werde ich nach meiner Rückkehr Ihre Nachricht beantworten.In dringenden Fällen erreichen Sie uns unter [email protected] oder Tel. 0049 5031 9408-0.Vielen herzlichen Dank.Note: This is an automated response to your message "Re: [ruby-net-ldap] UTF-8 encoding fix. (#44)" sent on 06.02.2013 20:24:10. This is the only notification you will receive while this person is away. |
This is still an issue two years later. Fortunately I was able to fix it using the gemfile change suggested by sebi. |
I was having an issue where the AD server was sending back bad utf-8 code ( \x82 I believe was the code value ). I'm currently using this fix in a production scenario. I would love to get some feedback on if this is a valid fix.