Skip to content
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.

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

Bad request 400 after new update #5793

Closed
kartik-v opened this issue Oct 28, 2014 · 5 comments
Closed

Bad request 400 after new update #5793

kartik-v opened this issue Oct 28, 2014 · 5 comments
Labels
severity:important status:to be verified Needs to be reproduced and validated. type:bug Bug

Comments

@kartik-v
Copy link
Contributor

Getting this for ajax/post submissions after updating to latest dev version. As discussed in #4497 - not sure if the problem is related. Problem resolves on reverting back to previous version of the yii2 repo.

@kartik-v kartik-v changed the title Bad request #400 after new update Bad request 400 after new update Oct 28, 2014
@qiangxue
Copy link
Member

Which version works?

@qiangxue qiangxue added status:to be verified Needs to be reproduced and validated. type:bug Bug labels Oct 28, 2014
@qiangxue qiangxue added this to the 2.0.1 milestone Oct 28, 2014
@kartik-v
Copy link
Contributor Author

I have not tracked the versions before composer update. This is the change log status of the yii2 version which does not apparently have the problem:

Yii Framework 2 Change Log

2.0.1 under development

@qiangxue
Copy link
Member

Based on this changelog, the breaking change should be introduced on or after Oct 24. However, I reviewed every commit and couldn't find anything related.

@qiangxue
Copy link
Member

Do you have code snippet to reproduce this issue?

@kartik-v
Copy link
Contributor Author

Its just a simple javascript triggered ajax form submit for a form rendered via Html::beginForm.

However, I have some headway on this problem. I tried a new app install and it did not have the problem. So I have purged my vendor folder on my web host and did a new composer update and the problem is gone.

Reasons:

  • could be some bad/incorrect composer update earlier
  • OR something more recent which fixes this

Closing this.

@cebe cebe removed this from the 2.0.1 milestone Oct 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity:important status:to be verified Needs to be reproduced and validated. type:bug Bug
Projects
None yet
Development

No branches or pull requests

3 participants