Comments (14)
We figured out the reason for this, mechanize seems to be processing the value of the cookie and removing the surrounding quotes in it. But LinkedIn seems to have changed something (internally) that made it choke if those quotes are not there.
So, mechanize should follow the RFC([http://www.ietf.org/rfc/rfc2109.txt]) and don't do any processing in the value.
from mechanize.
If you could please submit a failing test case for this, it would be a huge help in fixing it. Based on the above description, I don't have any easy way to reproduce this issue.
from mechanize.
This is the cookie generated by Mechanize alone, which doesn't work:
#<Mechanize::Cookie:0x64bbb50
@comment=nil,
@comment_url=nil,
@discard=nil,
@Domain="www.linkedin.com",
@expires=nil,
@max_age=nil,
@name="JSESSIONID",
@path="/",
@PORT=nil,
@secure=false,
@value="ajax:0403970942817037868",
@Version=1>,
This is the working cookie:
#<Mechanize::Cookie:0x60f62d0
@comment=nil,
@comment_url=nil,
@discard=nil,
@Domain="www.linkedin.com",
@expires=nil,
@max_age=nil,
@name="JSESSIONID",
@path="/",
@PORT=nil,
@secure=false,
@value=""ajax:0067975378067751123"",
@Version=0>,
from mechanize.
Adding:
I had to manually correct (add double quotes) these three cookies to get it to work:
leo_auth_token
s_leo_auth_token
JSESSIONID
from mechanize.
This is exactly what we did to make it work, it seems that mechanize is ignoring quotes when they are needed.
from mechanize.
I just sent a patch to the Mechanize Users mailing list with a test case that hopefully captures this issue.
from mechanize.
rossf7's tests and a fix at http://github.com/smparkes/mechanize/commit/631ce39f9d4843f62aefc6cdbb2b4576a2f5bd6b
from mechanize.
Can someone send a pull request for this? Would make my life easier ... :) Thank you for the extra effort!
from mechanize.
Ah - just saw the pull request. Never mind!
from mechanize.
Someone already merged it in. Shrug.
from mechanize.
Yeah, Aaron went on a tear yesterday. (Thanks Aaron.)
from mechanize.
Hi,
I can't login on linkedin using mechanize.
Here is the script I'm using:
require 'rubygems'
require 'mechanize'
agent = Mechanize.new
page = agent.get('https://www.linkedin.com/secure/login')
form = page.form('login')
form.session_key = 'my_email_login'
form.session_password = 'my_password'
form.click_button
I've tried several different ways to login, I also tried the script above but I always have the same response:
=> #<Mechanize::Page
{url #<URI::HTTPS:0xc8105b8 URL:https://www.linkedin.com/secure/login>}
{meta}
{title nil}
{iframes}
{frames}
{links #<Mechanize::Page::Link "click here" "http://www.linkedin.com/home">}
{forms}>
I have been able to login on some other systems, I don't know why it doesn't work on linkedin.
from mechanize.
This issue is closed. If you're looking for support on how to use mechanize, please email the mechanize-users mailing list. Thanks!
from mechanize.
No problemo, it works now anyway :)
Cheers!
from mechanize.
Related Issues (20)
- Heroku Stack and OpenSSL security HOT 3
- Hack to fix the "unsafe legacy renegotiation disabled" error
- Error 403 on heroku HOT 1
- wikipedia_links_to_philosophy.rb currently broken HOT 3
- Trouble when having so much li tags? HOT 1
- libxml2 2.11.x emitting error "FATAL: input conversion failed due to input error" on encoding errors HOT 2
- Per instance OpenSSL params set
- Mechanize doesn't raise Mechanize::ResponseCodeError if error happened before getting the response HOT 3
- Vite Dev server crachses due to a circular reference in a symlink
- explore: mechanize failures when running with libxml2 head HOT 2
- Feature request: print a warning if you call `Form#submit` without specifying a `button` if there are multiple HOT 3
- `Mechanize::File` overrides the `File` base class HOT 3
- 403 error on scrapper but website is accessible on browser
- Add nkf as dependency for Ruby 3.4 support HOT 3
- Compatibility Inquiry: mechanize 2.10.0 with Ruby 3.3.0 HOT 4
- A
- ruby-head test failures related to the HTTP::Cookie API
- [Documentation] More examples? Specifically for imgur + ruby.
- Issue 403 when connecting to page with redirects
- tidy: do not send deprecated headers HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mechanize.