Skip to content
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

beta23 crashes on oauth2 #1211

Closed
r10s opened this issue Jan 24, 2020 · 4 comments · Fixed by #1219
Closed

beta23 crashes on oauth2 #1211

r10s opened this issue Jan 24, 2020 · 4 comments · Fixed by #1219
Labels
bug Something is not working

Comments

@r10s
Copy link
Member

r10s commented Jan 24, 2020

{Received DC_EVENT_CONFIGURE_PROGRESS(20 ‰)}
{Received DC_EVENT_CONFIGURE_PROGRESS(200 ‰)}
ThreadId(5) src/configure/mod.rs:451: checking internal provider-info for offline autoconfig
ThreadId(5) src/configure/mod.rs:478: no offline autoconfig found
ThreadId(5) src/configure/read_url.rs:12: Requesting URL https://autoconfig.gmail.com"/mail/config-v1.1.xml?emailaddress=%22susisorgilos%40gmail%2Ecom%22
thread 'reqwest-internal-sync-runtime' panicked at 'a parsed Url should always be a valid Uri: InvalidUri(InvalidUriChar)', src/libcore/result.rs:1165:5
stack backtrace:
   0: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
   1: core::fmt::write
   2: std::io::Write::write_fmt
   3: std::panicking::default_hook::{{closure}}
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: rust_begin_unwind
   7: core::panicking::panic_fmt
   8: core::result::unwrap_failed
   9: <std::future::GenFuture<T> as core::future::future::Future>::poll
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread '<unnamed>' panicked at 'event loop thread panicked', /Users/bpetersen/.cargo/registry/src/github.com-1ecc6299db9ec823/reqwest-0.10.0/src/blocking/client.rs:748:5
stack backtrace:
   0: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
   1: core::fmt::write
   2: std::io::Write::write_fmt
   3: std::panicking::default_hook::{{closure}}
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::begin_panic
   6: reqwest::blocking::client::event_loop_panicked
   7: <std::future::GenFuture<T> as core::future::future::Future>::poll
   8: reqwest::blocking::request::RequestBuilder::send
   9: deltachat::configure::read_url::read_url
  10: deltachat::configure::auto_mozilla::moz_autoconfigure
  11: deltachat::configure::JobConfigureImap
  12: <core::iter::adapters::Map<I,F> as core::iter::traits::iterator::Iterator>::try_fold
  13: deltachat::job::job_perform
  14: deltachat::job::perform_inbox_jobs
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
@r10s
Copy link
Member Author

r10s commented Jan 24, 2020

the requested url

https://autoconfig.gmail.com"/mail/config-v1.1.xml?emailaddress=%22susisorgilos%40gmail%2Ecom%22

in fact looks weird. there is a bad quote between the domain and the path and also the %22 quotes around the address seems wrong.

EDIT: the email address in param.addr given to utf8_percent_encode() is already literally quoted (all tested with the repl tool, btw). this is wrong, but the real issue is probably the first quote.

@r10s
Copy link
Member Author

r10s commented Jan 24, 2020

k, i think i found the reason, the email address contains literally quotes, so part after the @ gets one quote as well.

maybe another issue is that the app crashes (the url is just a probe and would not work anyway - so errors here could just be ignored)

@link2xt
Copy link
Collaborator

link2xt commented Jan 24, 2020

seanmonstar/reqwest#668

@r10s
Copy link
Member Author

r10s commented Jan 24, 2020

seanmonstar/reqwest#668

interesting, thank you!

however, the quote should not come into the url at all :)

@r10s r10s added the bug Something is not working label Aug 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants