The test currently does not succeed, I think because we also need at
least...
Access-Control-Allow-Credentials: true
...for the cookie.
Regards,
Michael
Am 09.06.2014 03:06, schrieb Mark
Webb-Johnson:
Looking at the references mozilla document, it seems that our API
use cases fall within the 'simple' approach.
I have changed the tmc.openvehicles.com
server to return "Access-Control-Allow-Origin: *" for all
requests, and that is live now. I have also put up the
simpleclient.htm for testing at:
...static values except for the "ORIGIN" variable, which
needs to echo back the "Origin:" header from the
request. I'm not familiar with AnyEvent::HTTPD, maybe
something like
Bug
squished. Live on tmc now
(and pushed to github).
Neat
web page. Shows promise.
Regarding
the CORS, I’m very
willing to make the
changes - just not
really sure what headers
exactly need to be
added. Anyone here know
what I would need to
add?
Regards,
Mark.
On 6 Jun,
2014, at 3:03 pm,
Michael Balzer
<dexter@expeedo.de>
wrote:
Nikolay,
you found an API
server bug :-)
Solution: delete all
domain cookies for "openvehicles.com"
from your browser
before using the
API.
The API server gets
confused by multiple
cookies. If you
visit www.openvehicles.com
before using the
API, you get a
persistent PHP
session cookie like
this:
Name
SESS619b2b3f204291df32506531f8b446dd
Host .openvehicles.com
Pfad /
As the host defines
".openvehicles.com"
and path "/", this
cookie also gets
sent to the API
host, which then
confuses this one
with the
"ovmsapisession"
cookie, i.e.
I am
getting "login
ok" when
pressing on
the login
button, but
then all the
other buttons
are giving
"authentication
error"
message.
I
could check
that the
cookie is sent
with the
request, but
the server
seems to
respond with
the 400 code.
I
tried in Chrome.
Where, how do
you use the
page?
Nikolay
On
Thursday, June
5, 2014 10:59
PM, Michael
Balzer <dexter@expeedo.de>
wrote:
Nikolay,
that's right,
I intend to
get this
running
without an
otherwise
necessary
proxy, i.e.
for local HTML
pages on
mobile devices
or the like.
I've been in
contact with
Mark about
CORS on the
perl server.
A server could
of course be
used, most
simply the
HTTP API
itself could
deliver the
client page,
but CORS
should now
enable to cope
without and
open possible
cross origin
data/control
integrations.
Not sure about
static pages
for this
though, not
yet tested. I
think it would
be cool to
just load some
HTML file in
your browser
and have a
graphical OVMS
client.
The "code" is
currently just
a first test
bed HTML page
to interact
with the HTTP
API. No
graphics, just
a simple table
view. Works,
but is clumsy
as hell.
Try yourself,
I've attached
it.
Regards,
Michael
Am
05.06.2014
11:26, schrieb
Nikolay
Shishkov:
Hi
Michael,
I
am very
interested in
the "Browser
client using
HTTP API and
jQuery/Flot
for
visualization".
From the
comment that
CORS is needed
I suspect you
want to have
the html5 page
locally and
then fetch
data from the
server while
using other
sources for
context data.
Have
you considered
running this
on a separate
server that
serves as a
gateway to the
TMC server?
Have
you uploaded
the code
somewhere?
I
have been
playing around
with C# client
and was
thinking of
using it on an
asp.net server...
Nikolay
On
Wednesday,
June 4, 2014
11:22 PM,
Michael Balzer
<dexter@expeedo.de>
wrote:
Am
04.06.2014
07:38, schrieb
Gianluca
Magalotti:
> For
nice2have
features I'll
wait for your
list (I have
my personal
> list too
but maybe
we'll have a
later focus on
that)
So here it is.
If other Twizy
drivers would
like to add
their ideas,
you're
welcome.
I'll do my
best to check
new ideas
against my
collected
knowledge of
what's
possible up to
now and give
you some
feedback.