Switch to ArdorForum

Hi Guys,

Sorry for the late reply, I haven't logged in recently.

STSH issuer account:
NXT-KUQ3-SYHL-E4BE-B2BL5
Current account value is approximately 25,000 NXT

STSH was started as diversified portfolio with steady and consistent payouts 1 NXT/week, mining was only one of the avenues for revenue generation. But somehow after first couple of months got sucked into ltcgear fiasco, and by the end of november 2014 ltcgear became the main moneymaker for STSH, even after december 2014 when ltcgear stopped making payments I still continued to believe in them and made some payments using my own funds.

Fast forward to November 2015 and it has become clear that ltcgear is a classic scam, they are making payments now but after charging more fees from there existing clients and there are several dozen people who have made the new payments and are happy with there new payments. I think ltcgear will keep milking as long as they can find new suckers.

I am going through some tough time personally and financially. Even NXT has lost 80% of its value since the time STSH was started. Nothing against NXT its just the phase of my life I am going through.

Over the next few months I will be closing this asset. More details when I have personal funds and fresh mindset to execute this procedure. Currently I am not active in crypto, neither NXT so I don't have any exact plan of when or how it will be executed.

My apologies for the way things panned out, I didn't intend or wish to cause loss to anyone but inspire of best of my intentions it has come to this.

I am sorry and please forgive me.

I can't say I trust what you said above regarding the reasons for closing this asset, since it is part of my own nature to not trust anyone that easily. I also will not go into the topic of whether you could have done a better job in managing and communicating the status of this asset.

However, of all the assets that I have owned that have failed (which is a lot ) you are the first asset issuer that have communicated with your asset holders until the end and have issued an apology. That being said, as a STSH asset holder, I thank you for this and wish you the very best in your life.

Hello pocesar!

Sorry for the (very) late reply, I just got time to investigate this issue. If you were able to get around this issue let me know. I will post my investigation results anyways.

I created a very small webapp to test CORS support and it seems to be working right in the majority of the cases. The only exception is when the ajax request includes a custom header, and this is because the configuration needs to explicitly list any custom headers that it allows for any CORS request, not a wildcard '*'.

For example: some time ago, some of the popular JS libraries (e.g. jquery) were adding a 'X-Requested-With: XMLHttpRequest' header by default in HTTP requests to indicate  that the request was originated using Ajax. In order to make CORS work correctly, the server side CORS configuration should explicitly specify that it allows the 'X-Requested-With' header.
But now these JS libraries dropped that header and the configuration is not necessary unless the header is being explicitly added by the developer.

The other case is when the Content-Type header is other than application/x-www-form-urlencoded, multipart/form-data, or text/plain. In this case you need to explicitly specify in the server-side configuration that the Content-Type header is allowed. But the NXT UI specifies application/x-www-form-urlencoded since requests to the NXT API server do not include content in the request body, so the current configuration is fine.


Going back to your case, you said that:

I'm trying to reach it through the browser, since it uses different ports, the CORS request is failing because the answer is malformed

What are you trying to reach through the browser?

1) Is it the nxt UI?
2) Or are you trying to execute an API call through the browser so that it displays the response in the browser page?

AFAIK, in both cases, the HTTP request will not use CORS since in the first case the same server hosts the UI and the API server, and in the second case Ajax (javascript) is not used to fetch the contents. So in both cases CORS is not needed.

Did you verified that the 'nxt.allowedBotHosts' includes the ip address of the machine from which you are accessing the nxt instance?

- mess

I nominate you cobaltskky . Even though I don't know you, you seem to be a trustworthy person.

maybe 0.0082 per share

I also got payed as if the rate was something similar (not exactly) to the figure you mention, and not 0.082 per share. I already sent a pm to valarg/coinomat asking to see if they could help me clarify this out.

Hmm maybe I can try to do that after I do this 1 last thing..  what you are talking about is a good bit more tricky though

Yep... I think it will imply a bit of more work, but that way the user would have all the information in a single page, which I think will result in a better user experience. Right now the page is OK though, so there is no hurry in doing what I suggested (if it seems like a good idea).