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

Server Error when preview comment having char < 0x1f, or char==0x7f #29

Closed
paulej72 opened this Issue Apr 24, 2015 · 8 comments

Comments

Projects
None yet
4 participants
@paulej72
Contributor

paulej72 commented Apr 24, 2015

From @marty-b on March 29, 2015 21:28

Tried to submit a comment to: https://dev.soylentnews.org/article.pl?sid=15/03/29/1622202
1.) Viewed story
2.) Clicked on Reply button
3.) Entered comment title: "0x7f - POT"
4.) Selected "Plain Old Text" from the Drop-Down list
5.) Clicked on 'Preview' button.
6.) Got server error:
OK

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, slash@dev.soylentnews.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

7.) paulej72 provided this snippet from logs:

[Sun Mar 29 20:49:50 2015] [error] /comments.pl:ModPerl::ROOT::ModPerl::Registry::srv_soylentnews_2eorg_rehash_site_soylent_2dmainpage_htdocs_comments_2epl:/srv/soylentnews.org/rehash/site/soylent-mainpage/htdocs/comments.pl:506:cannot getSkin for empty skid='0' ;; Which was called by:ModPerl::ROOT::ModPerl::Registry::srv_soylentnews_2eorg_rehash_site_soylent_2dmainpage_htdocs_comments_2epl:/srv/soylentnews.org/rehash/site/soylent-mainpage/htdocs/comments.pl:329
[Sun Mar 29 20:51:00 2015] [error] Cannot decode string with wide characters at /srv/soylentnews.org/perl/lib/perl5/site_perl/5.20.1/x86_64-linux-thread-multi/Encode.pm line 241.\n

Copied from original issue: SoylentNews/slashcode#435

@paulej72

This comment has been minimized.

Show comment
Hide comment
@paulej72

paulej72 Apr 24, 2015

Contributor

From @marty-b on March 29, 2015 21:30

Missing one step:
3.5) In the text entry area, insert a single character: 0x7f, i.e. "�"

Contributor

paulej72 commented Apr 24, 2015

From @marty-b on March 29, 2015 21:30

Missing one step:
3.5) In the text entry area, insert a single character: 0x7f, i.e. "�"

@paulej72

This comment has been minimized.

Show comment
Hide comment
@paulej72

paulej72 Apr 24, 2015

Contributor

From @NCommander on March 30, 2015 5:15

Ugh. I'm guessing this is a problem with perl 5.20 vs. mod_perl 2. Paging
TMB.

On Sun, Mar 29, 2015 at 5:30 PM, Marty B notifications@github.com wrote:

Missing one step:
3.5) In the text entry area, insert a single character: 0x7f, i.e. " "


Reply to this email directly or view it on GitHub
SoylentNews/slashcode#435 (comment)
.

Contributor

paulej72 commented Apr 24, 2015

From @NCommander on March 30, 2015 5:15

Ugh. I'm guessing this is a problem with perl 5.20 vs. mod_perl 2. Paging
TMB.

On Sun, Mar 29, 2015 at 5:30 PM, Marty B notifications@github.com wrote:

Missing one step:
3.5) In the text entry area, insert a single character: 0x7f, i.e. " "


Reply to this email directly or view it on GitHub
SoylentNews/slashcode#435 (comment)
.

@NCommander

This comment has been minimized.

Show comment
Hide comment
@NCommander

NCommander Apr 30, 2015

Contributor

I can't reproduce this anymore; I copy and pasted in quite a few single unicode characters, including 0x7f (division sign), and failed to get the server to up and chuck. I think we can close this, but I'd like @martyb to reconfirm it

Contributor

NCommander commented Apr 30, 2015

I can't reproduce this anymore; I copy and pasted in quite a few single unicode characters, including 0x7f (division sign), and failed to get the server to up and chuck. I think we can close this, but I'd like @martyb to reconfirm it

@marty-b

This comment has been minimized.

Show comment
Hide comment
Contributor

marty-b commented Apr 30, 2015

@NCommander

This comment has been minimized.

Show comment
Hide comment
@NCommander

NCommander May 2, 2015

Contributor

I appear to have accidently fixed this on dev: the following text: <a href="http://www.google.com/search?q="♥">proper no longer 500s. However, the link is missing the unicode char; this behavior is consistent with production. I have no idea how I fixed it, I didn't make a code change but I was screwing with Apache's configuration to move the vhost log into error log to get feedback.

Contributor

NCommander commented May 2, 2015

I appear to have accidently fixed this on dev: the following text: <a href="http://www.google.com/search?q="♥">proper no longer 500s. However, the link is missing the unicode char; this behavior is consistent with production. I have no idea how I fixed it, I didn't make a code change but I was screwing with Apache's configuration to move the vhost log into error log to get feedback.

@NCommander

This comment has been minimized.

Show comment
Hide comment
@NCommander

NCommander May 2, 2015

Contributor

a href="http://www.google.com/search?q="♥"proper/a

removing < > to get this to post

Contributor

NCommander commented May 2, 2015

a href="http://www.google.com/search?q="♥"proper/a

removing < > to get this to post

@NCommander

This comment has been minimized.

Show comment
Hide comment
@NCommander
Contributor

NCommander commented May 2, 2015

@TheMightyBuzzard

This comment has been minimized.

Show comment
Hide comment
@TheMightyBuzzard

TheMightyBuzzard May 6, 2015

Contributor

Believed to be fixed in #37

Contributor

TheMightyBuzzard commented May 6, 2015

Believed to be fixed in #37

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment