From: 이원영 <wy1115.lee@samsung.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "connman@lists.linux.dev" <connman@lists.linux.dev>
Subject: RE: Re: Query about ipv4 connman web page
Date: Wed, 29 Nov 2023 10:16:59 +0900 [thread overview]
Message-ID: <20231129011659epcms1p57c0faf7151f067f18be5cfef0229f1f9@epcms1p5> (raw)
In-Reply-To: CGME20231128052502epcms1p4a229137cf6d9bb65b8e463a873688e69@epcms1p5
Dear Marcel,
Thank you for quick fix.
It is very impressive experience for me.
I hope to ask the following questions.
1. Could you share the reason of "Connection timeout" if possible?
2. When I face ipv4.connman.net/online/status.html access issue, can I report to this way?
BR
Wonyoung Lee
--------- Original Message ---------
Sender : Marcel Holtmann <marcel@holtmann.org>
Date : 2023-11-28 18:55 (GMT+9)
Title : Re: Query about ipv4 connman web page
Hi Lee,
> I am testing connman on Tizen platform with the following URLs
> "https://protect2.fireeye.com/v1/url?k=a37d3ce5-c2f629d3-a37cb7aa-74fe485cbff1-0a4cc3ceca2ef108&q=1&e=e494d81d-c061-4755-8c99-c2c5c83bca0d&u=http%3A%2F%2Fipv4.connman.net%2Fonline%2Fstatus.html"
> "https://protect2.fireeye.com/v1/url?k=31efc497-5064d1a1-31ee4fd8-74fe485cbff1-e6408c7ba2f81bce&q=1&e=e494d81d-c061-4755-8c99-c2c5c83bca0d&u=http%3A%2F%2Fipv6.connman.net%2Fonline%2Fstatus.html"
>
>
> But when I test CURL GET request to those URLs, the response is CURLE 28 (Connection timeout)
> Could you help to fix those web service?
should be all back to normal now.
Regards
Marcel
next parent reply other threads:[~2023-11-29 1:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231128052502epcms1p4a229137cf6d9bb65b8e463a873688e69@epcms1p5>
2023-11-29 1:16 ` 이원영 [this message]
2023-11-29 12:49 ` Query about ipv4 connman web page Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231129011659epcms1p57c0faf7151f067f18be5cfef0229f1f9@epcms1p5 \
--to=wy1115.lee@samsung.com \
--cc=connman@lists.linux.dev \
--cc=marcel@holtmann.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).