Skip to content

Une mise à jour #9

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.

Sign up for GitHub

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

Merged
loicfrering merged 1 commit into from
Jan 4, 2012
Merged

Une mise à jour #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Rajout d'information sur le post "les subtilité du login en JS"
  • Loading branch information
@feugy
feugy committed Jan 3, 2012
commit c9a826128b87138466fccdc93f0caa683e53916a
4 changes: 4 additions & 0 deletions _posts/2011-10-19-subtilites-du-login.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,6 +98,10 @@ Cela implique:

Donc généralement, mon service web propose une API POST qui ne fait rien et renvoie une page vide, et j'utilise une iframe masquée.

>**Edit**
Les dernières versions de Chrome (15+) impose une nouvelle contrainte : il faut que le retour du serveur soit non vide.
Donc votre "fausse API" POST doit renvoyer quelque chose (y compris une chaîne vide), mais en aucun cas un code HTTP 204 (OK BUT NO CONTENT)

**index.html**

{% highlight html %}
Expand Down