The Movie Database-ondersteuning

I've been reading the API documentation and note that the validate_with_login method is a GET operation. You have already documented how this would send the username and password in the plain, so do not recommend its use. However, if you allowed the username and password fields to be passed in a POST, implementors could opt to use the HTTPS interface to reduce the exposure.

I know that the TLS/SSL session covers the connection to the server, before the query is sent, so the data is not necessarily sent in the plain, but outbound logging by the user agent is more likely to include the query than the postdata.

Is there any reason you elected to go with a GET, rather than a POST here?

1 antwoord (op blad 1 van 1)

Jump to last post

Hi jimbobmcgee,

There's no reason in particular, just lack of a request. I've created a new ticket for this here, and will look at it when I have some time. It's pretty straightforward to add so I'll try to get to it sooner than later.

Cheers.

Kan ’n rolprent of TV-program nie vind nie? Teken aan om dit te skep.

Globaal

s fokus op soekbalk
p open profielkieslys
esc sluit ’n oop venster
? open sneltoetsvenster

Op mediablaaie

b gaan terug (na ouer waar van toepassing)
e gaan na wysigblad

Op TV-seisoenblaaie

(regterpyl) gaan na volgende seisoen
(linkerpyl) gaan na vorige seisoen

Op TV-episodeblaaie

(regterpyl) gaan na volgende episode
(linkerpyl) gaan na vorige episode

Op alle beeldblaaie

a open beeldtoevoegvenster

Op alle wysigingsblaaie

t open vertaalkieser
ctrl+ s dien form in

Op besprekingsblaaie

n skep nuwe bespreking
w tokkel kykstatus
p tokkel openbaar/privaat
c tokkel maak oop/toe
a open aktiwiteit
r reageer op bespreking
l gaan na laaste reaksie
ctrl+ enter dien u boodskap in
(regterpyl) volgende blad
(linkerpyl) vorige blad

Instellings

Wil u hierdie item gradeer of tot ’n lys toevoeg?

Teken aan