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.

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

Jump to bottom

Lack testing in FastCGI error #2

Open
yookoala opened this issue Jan 18, 2016 · 2 comments
Open

Lack testing in FastCGI error #2

yookoala opened this issue Jan 18, 2016 · 2 comments
Assignees
@yookoala
Labels
enhancement
Milestone
v0.4

Comments

@yookoala
Copy link
Owner

Need more test case in triggering FastCGI Stderr steam output. Make sure no read/write block.
@yookoala
Copy link
Owner Author

yookoala commented Feb 2, 2018 •
edited
Loading

Since node-fastcgi has better support to error stream writing, its best to do the error stream handling as part of the node-fastcgi example.

Reference: #17

@yookoala yookoala self-assigned this Feb 2, 2018
@yookoala yookoala added this to the v1.0 milestone Feb 9, 2018
This was referenced Feb 9, 2018
Open
Closed
@yookoala
Copy link
Owner Author

0d16770 partially solved this issue. But I think some inspection to error stream output is still needed.

@yookoala yookoala modified the milestones: v1.0, v0.4 Jul 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yookoala yookoala

Labels
enhancement
Projects
None yet
Milestone
v0.4
Development

No branches or pull requests
1 participant
@yookoala