-
-
Notifications
You must be signed in to change notification settings - Fork 755
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
File uploading with aiohttp (status 500) #975
Comments
fr33mang
pushed a commit
to fr33mang/connexion
that referenced
this issue
Jun 14, 2019
Closed
fr33mang
pushed a commit
to fr33mang/connexion
that referenced
this issue
Jun 14, 2019
fr33mang
pushed a commit
to fr33mang/connexion
that referenced
this issue
Jun 14, 2019
fr33mang
pushed a commit
to fr33mang/connexion
that referenced
this issue
Jun 14, 2019
kornicameister
pushed a commit
to kornicameister/connexion
that referenced
this issue
Jul 5, 2019
changes: - different handling for multipart and non-multipart requests - tests confirming the behavior - minor list to typle changes for collection that ought to be immutable Fixes spec-first#975
kornicameister
pushed a commit
to kornicameister/connexion
that referenced
this issue
Jul 9, 2019
changes: - different handling for multipart and non-multipart requests - tests confirming the behavior - minor list to typle changes for collection that ought to be immutable Fixes spec-first#975
kornicameister
pushed a commit
to kornicameister/connexion
that referenced
this issue
Jul 9, 2019
changes: - different handling for multipart and non-multipart requests - tests confirming the behavior - minor list to typle changes for collection that ought to be immutable Fixes spec-first#975
Ping. I need solved for the problem. What is status the issue? |
@kornicameister create new PR. |
ddurham2
added a commit
to ddurham2/connexion
that referenced
this issue
Apr 22, 2020
- Taken mostly from existing PR: spec-first#987
Is there already a solution on that? I have the problem that I definitely need to upload files to the server and this bug seems to still persist. |
Closed
RichardBruskiewich
pushed a commit
to STARInformatics/connexion
that referenced
this issue
Mar 11, 2021
RobbeSneyders
pushed a commit
that referenced
this issue
Feb 18, 2022
* Added unit tests to demonstrate the problems of #975 - Taken mostly from existing PR: #987 * now splitting out multipart POSTs into files[] and form[], handling duplicate keys as the rest of connexion expects - Based parly on existing PR: #987 * rewrote how operations/openapi.py::_get_body_argument() works to better build the arguments[] list according to what the spec says and what the handler accepts. This fixes a bug when requests contain mixed files and form values and the handler is expecting variable names matching the request property names. * Adding unit tests to improve code converage test * post merge fixes - using 'async' keyword now in new unit test file * unit test improvements -- now testing the contents of the files we upload too * making some code a bit clearer regarding duplicate names of file submissions * fixing up unit tests since merging main * fixing isort-check-tests and flake8 * clarified a comment * comment correction * after discussions with maintainer, reverted _get_body_argument back to the original where it does not attempt to break out the body into individual arguments for the handler. But left in changes that make the normal behavior of not passing a body argument to a handler without one more consistent when the body itself is empty or not an object type. * fixing unit tests after after reverting _get_body_argument behavior
Should be fixed by #1222 |
vbxx3
pushed a commit
to Savannah-Group/connexion
that referenced
this issue
Apr 9, 2022
* Added unit tests to demonstrate the problems of spec-first#975 - Taken mostly from existing PR: spec-first#987 * now splitting out multipart POSTs into files[] and form[], handling duplicate keys as the rest of connexion expects - Based parly on existing PR: spec-first#987 * rewrote how operations/openapi.py::_get_body_argument() works to better build the arguments[] list according to what the spec says and what the handler accepts. This fixes a bug when requests contain mixed files and form values and the handler is expecting variable names matching the request property names. * Adding unit tests to improve code converage test * post merge fixes - using 'async' keyword now in new unit test file * unit test improvements -- now testing the contents of the files we upload too * making some code a bit clearer regarding duplicate names of file submissions * fixing up unit tests since merging main * fixing isort-check-tests and flake8 * clarified a comment * comment correction * after discussions with maintainer, reverted _get_body_argument back to the original where it does not attempt to break out the body into individual arguments for the handler. But left in changes that make the normal behavior of not passing a body argument to a handler without one more consistent when the body itself is empty or not an object type. * fixing unit tests after after reverting _get_body_argument behavior
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Connexion return 500 error.
My swagger scheme:
Handler:
Html form:
Expected behaviour
FileField(name='fileName', filename='script.sql', file=<_io.BufferedRandom name=12>, content_type='application/octet-stream', headers=<CIMultiDictProxy('Content-Disposition': 'form-data; name="fileName"; filename="script.sql"', 'Content-Type': 'application/octet-stream')>)
Actual behaviour
The text was updated successfully, but these errors were encountered: