Otdfbt

Can I make plugins required?

Grover algorithm for a database search: where is the quantum advantage?

Generate a Graeco-Latin square

Is the term 'open source' a trademark?

How does an ordinary object become radioactive?

Is it possible to 'live off the sea'

Preventing employees from either switching to competitors or opening their own business

What is the actual quality of machine translations?

At what point in time did Dumbledore ask Snape for this favor?

What is wrong with this proof that symmetric matrices commute?

C++ Arduino IDE receiving garbled `char` from function

What can I, as a user, do about offensive reviews in App Store?

What is the fastest method to figure out which keys contain certain notes?

Overlapping String-Blocks

SQL counting distinct over partition

Can the poison from Kingsmen be concocted?

Winning Strategy for the Magician and his Apprentice

Cycle through MeshStyle directives in ListLinePlot

PhD - Well known professor or well known school?

What's up with this leaf?

What makes Ada the language of choice for the ISS's safety-critical systems?

What ways have you found to get edits from non-LaTeX users?

eval() in Lightning Web Components

Déjà vu, again?

New line character %250A in URL: Apache throws 404 error

Unable to run local version of example.com on browserApache 404 Error When 'index' is in the PathVarnish / Apache redirecting to backend port 8080Ubuntu Apache Gives Internal Server Error 500Apache, mod_wsgi, Django Error When Not SSH'd In To ServerVirtualServer reverseproxy works locally, but not from clientGetting Drupal or Apache to try a proxy on 404ProxyPassReverse Not Working with 302 RedirectHide Original URL using mod_proxyNot able to clone into repository on gitlab through port 80

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

0

This is example of the script path which causes problem:

http://example.com/index/index/tokenID/345%250Atest

If I try to visit this link on the production server I receive 404 error. If I try to visit it on local machine:

localhost:8080/index/index/tokenID/345%250Atest

everything works well.

Both servers on Apache. Production server - Cent OS, localhost - Ubuntu. It looks like there is some configuration in Apache file that I forgot to set.

apache-2.2 url

share|improve this question

asked Nov 12 '14 at 1:21

TamaraTamara

1015

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  answered here: stackoverflow.com/a/3871762/503621 - use %0A for n and %0D for r
  
  – bshea
  Jan 21 at 16:11
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Using %250A in a online url decoder produces bad result. Maybe try 'hashing' the 'token' first (a-Z / 0-9 chars only?) before adding/encoding to URL? Or run through script first to replace bad ones with above?
  
  – bshea
  Jan 21 at 16:23
  
  

  
  
  
  

add a comment | 

0

This is example of the script path which causes problem:

http://example.com/index/index/tokenID/345%250Atest

If I try to visit this link on the production server I receive 404 error. If I try to visit it on local machine:

localhost:8080/index/index/tokenID/345%250Atest

everything works well.

Both servers on Apache. Production server - Cent OS, localhost - Ubuntu. It looks like there is some configuration in Apache file that I forgot to set.

apache-2.2 url

share|improve this question

asked Nov 12 '14 at 1:21

TamaraTamara

1015

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  answered here: stackoverflow.com/a/3871762/503621 - use %0A for n and %0D for r
  
  – bshea
  Jan 21 at 16:11
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Using %250A in a online url decoder produces bad result. Maybe try 'hashing' the 'token' first (a-Z / 0-9 chars only?) before adding/encoding to URL? Or run through script first to replace bad ones with above?
  
  – bshea
  Jan 21 at 16:23
  
  

  
  
  
  

add a comment | 

This is example of the script path which causes problem:

http://example.com/index/index/tokenID/345%250Atest

If I try to visit this link on the production server I receive 404 error. If I try to visit it on local machine:

localhost:8080/index/index/tokenID/345%250Atest

everything works well.

Both servers on Apache. Production server - Cent OS, localhost - Ubuntu. It looks like there is some configuration in Apache file that I forgot to set.

apache-2.2 url

share|improve this question

asked Nov 12 '14 at 1:21

TamaraTamara

1015

http://example.com/index/index/tokenID/345%250Atest

localhost:8080/index/index/tokenID/345%250Atest

share|improve this question

asked Nov 12 '14 at 1:21

TamaraTamara

1015

share|improve this question

asked Nov 12 '14 at 1:21

TamaraTamara

1015

asked Nov 12 '14 at 1:21

TamaraTamara

1015

asked Nov 12 '14 at 1:21

TamaraTamara

1015

1 Answer
1

active

oldest

votes

0

From RFC 1738 specification (not the latest):

Thus, only alphanumerics, the special characters "$-_.+!*'(),", and
reserved characters used for their reserved purposes may be used
unencoded within a URL.

The current spec is RFC 3986

Now that statement above is for unencoded characters but yours is encoded. I haven't found the similar statement.

A URI is composed from a limited set of characters consisting of

digits, letters, and a few graphic symbols. A reserved subset of

those characters may be used to delimit syntax components within a

URI while the remaining characters, including both the unreserved set
and those reserved characters not acting as delimiters, define each

component's identifying data.

share|improve this answer

edited Nov 12 '14 at 1:32

answered Nov 12 '14 at 1:26

RobRob

297314

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hi, Rob. I don't understand your answer. I use urlencode() function in order to pass data in URL. Result of this function contains %250A which is url encoded character (new line symbol, as I understand). Why it can be handled by one type of the servers and can not by others?
  
  – Tamara
  Nov 12 '14 at 1:34
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Tamara I believe the encoded newline is %0A. %240A decodes to %0A.
  
  – BillThor
  Nov 12 '14 at 1:39
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @BillThor I thought %250A decodes to %0A. Anyway if I replace %250A with %0A it still doesn't work on the production server, but works on localhost.
  
  – Tamara
  Nov 12 '14 at 1:51
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Tamara You may not have the same content or same docroot on both systems. It is strange to have /index/index in the path, although this is legal. Having linefeeds in a filename is also strange. You may also have permission issues. Check the error log.
  
  – BillThor
  Nov 12 '14 at 1:56
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f643668%2fnew-line-character-250a-in-url-apache-throws-404-error%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

0

From RFC 1738 specification (not the latest):

Thus, only alphanumerics, the special characters "$-_.+!*'(),", and
reserved characters used for their reserved purposes may be used
unencoded within a URL.

The current spec is RFC 3986

Now that statement above is for unencoded characters but yours is encoded. I haven't found the similar statement.

A URI is composed from a limited set of characters consisting of

digits, letters, and a few graphic symbols. A reserved subset of

those characters may be used to delimit syntax components within a

URI while the remaining characters, including both the unreserved set
and those reserved characters not acting as delimiters, define each

component's identifying data.

share|improve this answer

edited Nov 12 '14 at 1:32

answered Nov 12 '14 at 1:26

RobRob

297314

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hi, Rob. I don't understand your answer. I use urlencode() function in order to pass data in URL. Result of this function contains %250A which is url encoded character (new line symbol, as I understand). Why it can be handled by one type of the servers and can not by others?
  
  – Tamara
  Nov 12 '14 at 1:34
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Tamara I believe the encoded newline is %0A. %240A decodes to %0A.
  
  – BillThor
  Nov 12 '14 at 1:39
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @BillThor I thought %250A decodes to %0A. Anyway if I replace %250A with %0A it still doesn't work on the production server, but works on localhost.
  
  – Tamara
  Nov 12 '14 at 1:51
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Tamara You may not have the same content or same docroot on both systems. It is strange to have /index/index in the path, although this is legal. Having linefeeds in a filename is also strange. You may also have permission issues. Check the error log.
  
  – BillThor
  Nov 12 '14 at 1:56
  

  
  
  
  

add a comment | 

0

From RFC 1738 specification (not the latest):

Thus, only alphanumerics, the special characters "$-_.+!*'(),", and
reserved characters used for their reserved purposes may be used
unencoded within a URL.

The current spec is RFC 3986

Now that statement above is for unencoded characters but yours is encoded. I haven't found the similar statement.

A URI is composed from a limited set of characters consisting of

digits, letters, and a few graphic symbols. A reserved subset of

those characters may be used to delimit syntax components within a

URI while the remaining characters, including both the unreserved set
and those reserved characters not acting as delimiters, define each

component's identifying data.

share|improve this answer

edited Nov 12 '14 at 1:32

answered Nov 12 '14 at 1:26

RobRob

297314

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hi, Rob. I don't understand your answer. I use urlencode() function in order to pass data in URL. Result of this function contains %250A which is url encoded character (new line symbol, as I understand). Why it can be handled by one type of the servers and can not by others?
  
  – Tamara
  Nov 12 '14 at 1:34
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Tamara I believe the encoded newline is %0A. %240A decodes to %0A.
  
  – BillThor
  Nov 12 '14 at 1:39
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @BillThor I thought %250A decodes to %0A. Anyway if I replace %250A with %0A it still doesn't work on the production server, but works on localhost.
  
  – Tamara
  Nov 12 '14 at 1:51
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Tamara You may not have the same content or same docroot on both systems. It is strange to have /index/index in the path, although this is legal. Having linefeeds in a filename is also strange. You may also have permission issues. Check the error log.
  
  – BillThor
  Nov 12 '14 at 1:56
  

  
  
  
  

add a comment | 

From RFC 1738 specification (not the latest):

Thus, only alphanumerics, the special characters "$-_.+!*'(),", and
reserved characters used for their reserved purposes may be used
unencoded within a URL.

The current spec is RFC 3986

Now that statement above is for unencoded characters but yours is encoded. I haven't found the similar statement.

A URI is composed from a limited set of characters consisting of

digits, letters, and a few graphic symbols. A reserved subset of

those characters may be used to delimit syntax components within a

URI while the remaining characters, including both the unreserved set
and those reserved characters not acting as delimiters, define each

component's identifying data.

share|improve this answer

edited Nov 12 '14 at 1:32

answered Nov 12 '14 at 1:26

RobRob

297314

share|improve this answer

edited Nov 12 '14 at 1:32

answered Nov 12 '14 at 1:26

RobRob

297314

answered Nov 12 '14 at 1:26

RobRob

297314

answered Nov 12 '14 at 1:26

RobRob

297314