Hi Jonh,
> One note: The original patch was supposed to handle 511 http status code,
> not wispr. see http://tools.ietf.org/html/rfc6585
I do not remember any portal using 511 status. At least the ones we
tested have not used it. However we have seen hotspots that are using
200 success status cod
One note: The original patch was supposed to handle 511 http status code,
not wispr. see http://tools.ietf.org/html/rfc6585
2013/2/19 Marcel Holtmann
> Hi Dan,
>
> > > > Plus, as I stated earlier, libxml will be required to handle Wispr
> > > > responses (and hotspot 2.0), which are legitimate
Hi Dan,
> > > Plus, as I stated earlier, libxml will be required to handle Wispr
> > > responses (and hotspot 2.0), which are legitimate XML trees. So, why not
> > > just add it as a dependency right now?
> >
> > that is a funny comment since within ConnMan, we are using GMarkup to
> > handle the
On Tue, 2013-02-19 at 01:45 +0100, Marcel Holtmann wrote:
> Hi Jonh,
>
> > Plus, as I stated earlier, libxml will be required to handle Wispr
> > responses (and hotspot 2.0), which are legitimate XML trees. So, why not
> > just add it as a dependency right now?
>
> that is a funny comment since w
Hi Jonh,
> Plus, as I stated earlier, libxml will be required to handle Wispr
> responses (and hotspot 2.0), which are legitimate XML trees. So, why not
> just add it as a dependency right now?
that is a funny comment since within ConnMan, we are using GMarkup to
handle the WISPr login. And actua
Hi Dan.
2013/2/11 Dan Williams
> On Mon, 2013-02-11 at 15:30 -0200, Jonh Wendell wrote:
> > In these patches I want to fix the 511-http-status. As it's something
> > new, of course most hotspots don't use that (including my employer).
> >
> > Almost all of them rely on 30X Moved with help of the
On Mon, 2013-02-11 at 15:30 -0200, Jonh Wendell wrote:
> In these patches I want to fix the 511-http-status. As it's something
> new, of course most hotspots don't use that (including my employer).
>
> Almost all of them rely on 30X Moved with help of the Wispr
> 'pseudo-protocol'. It's on my TODO
In these patches I want to fix the 511-http-status. As it's something new,
of course most hotspots don't use that (including my employer).
Almost all of them rely on 30X Moved with help of the Wispr
'pseudo-protocol'. It's on my TODO list to work on those scenarios. That
would touch only code in N
On Mon, 2013-02-11 at 10:06 -0600, Dan Williams wrote:
> On Mon, 2013-02-11 at 12:09 -0200, Jonh Wendell wrote:
> > From: Jonh Wendell
> >
> > libsoup already depends on libxml2 but we need to explicitly link
> > to it.
>
> At least we already theoretically required it; though is it possible to
On Mon, 2013-02-11 at 17:10 +0100, Bastien Nocera wrote:
> On Mon, 2013-02-11 at 10:06 -0600, Dan Williams wrote:
> > On Mon, 2013-02-11 at 12:09 -0200, Jonh Wendell wrote:
> > > From: Jonh Wendell
> > >
> > > libsoup already depends on libxml2 but we need to explicitly link
> > > to it.
> >
> >
On Mon, 2013-02-11 at 12:09 -0200, Jonh Wendell wrote:
> From: Jonh Wendell
>
> libsoup already depends on libxml2 but we need to explicitly link
> to it.
At least we already theoretically required it; though is it possible to
use GMarkup here instead of libxml2? GMarkup would be somewhat simpl
From: Jonh Wendell
libsoup already depends on libxml2 but we need to explicitly link
to it.
Signed-off-by: Jonh Wendell
---
configure.ac| 14 +++---
src/Makefile.am | 4 ++--
2 files changed, 13 insertions(+), 5 deletions(-)
diff --git a/configure.ac b/configure.ac
index 916561a.
12 matches
Mail list logo