471069 - Publish function incompatible with Network Solutions

Status: NEW

(SeaMonkey :: Composer, defect)

Description

[glf]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5

Sea Monkey cannot "Publish" to Network Solutions host.
Sea Monkey does not parse the username correctly:
  For example:
   ntsl1047777%02b4cbd
Sea Monkey does not handle the "%" sign correctly.

Reproducible: Always

Steps to Reproduce:
1.Purchase Network Solutions hosting.
2.Configure SM username, password, location for the host
3. Try to publsh. Either fails with an "unsuccessful" or is "successful" but the file does not transfer.
4. Try the same configuration using FileZilla. Works every time.
5. NetSol tech support has no clue.

Comment 1

[Serge Gautherie (:sgautherie)]

Which product/version are you using ?

Comment 2

[glf]

SeaMOnkey 1.1.14
3. Always fails. (I was reading it wrong). File never transfers using sea monkey publish function.

Comment 3

[Ian Neal]

Could you see if it works using SM2.3?

Comment 5

[Ian Neal]

Original reporter has commented via email that it is still an issue in SM2.3
Marking as confirmed due to the duplicate, though comments in that one do seem to indicate it is potentially an issue at the Network Solutions end.

Comment 6

[John S. Giltner, Jr.]

I think the problem is the % and SeaMonkey.  Doing a tcpdump I found that SeaMonkey is changing the % to \\\\0, not sure why.  But if you code %25 instead of just % it works fine.

My ID johnadmin%01fb3ce in the trace is johnadmin\\\\001fb3ce.  But if I enter my user-id as johnadmin%2501fb3ce, it works.

Comment 7

[John S. Giltner, Jr.]

Well, my last post did not turn out like I expected.  The % is changed to a single backward slash followed by a zero.  Not four followed by a zero.

Comment 8

[glf]

But the "%25" trick works?

Comment 9

[John S. Giltner, Jr.]

Yes, works like a charm.  Oh, I using SM 2.5 on Windows, so I don't know if that makes a difference.

Comment 10

[John S. Giltner, Jr.]

O.K. After a couple more traces and tests I think I know what is going on.  Someplace in SeaMonkey is interpreting the % sign in a way that it causes it to take the next two positions as a hex value and convert to octal.  

I tested by taking my normal id johnadmin%01fb3ce and changing the %01 to %1F.  What got sent was single backward slash 037 and 037 is the octal value of hex 1F.

I am assuming it has something to do with URL encoding as using %xx where xx represents a valid hex value of a "text" character you get the actual text character: %25 gets a %.

Hopefully this will help somebody who knows the code.  Until then you need to code %25 to get the percent sign in there.

Comment 11

[Philip Chee]

That sounds like a DUP of another Composer bug somewhere but I can't remember the number.