20. Solve: $2^x=16$. A. 2 B. 3 C. 4 D. 8 21. Solve: $5^x=25$. A. 1 B. 2 C. 5 D. 25 22. Solve: $3^{x+2}=81$. A. 2 B. 3 C. 4 D. 6 23. $\log _{10} 1000=$ : A. 2 B. 3 C. 10 D. 100 24. $\log _2 8=$ : A. 2 B. 3 C. 4 D. 8 25. If $\log X=1$, Then $x=$

Oct 27, 2009as the aforementioned rfc does not include any reference of encoding spaces as +, i guess using %20 is the way to go today. For example, "%20" is the percent-encoding for the binary. Sometimes the spaces get url encoded to the + sign, and some other times to %20.

What is the difference and why should this happen? The common space character is encoded as %20 as you noted yourself. The % character is encoded as %25.

@metabyter i think it is more technically correct to phrase the question as "in a url, should i encode the spaces using %20 or + in the query part of a url?" because while the example you show. Since it's not mentioned anywhere in the grammar, the only way to encode a space is with percent-encoding (%20). In fact, the rfc even states that spaces are delimiters and should be ignored:

Dec 16, 2012i am interested in knowing why '%20' is used as a space in urls, particularly why %20 was used and why we even need it in the first place. There must be something in the .net framework that should help, right?