Search Results

The question is a little confusing because of the comments. The compiler complains about type definitions for len and buf. And you say in the comments: //(need to declare a type here) len = last - fi …

One problem is here <form action="/quote.html" method="post">. There is not a quote.html in document root (it is in subdir templates), thus the 404. But do you really want the form action to be the ht …

The problem seems to be with alphavantage. Staff solution gives the same problem (as of 9:21 am et us, 27-july-2017). Upon reading the alphavantage doc, the High Usage tag got me wondering.... I tr …

There shouldn't be an need for allocating in lookup(). You should simply be returning the string literal, as described in the spec. Why is returning an allocated pointer a problem? … The call from main is const char* type = lookup(path);. When you allocate the local variable mime in lookup it gets a (new!) memory address. …

Scope. Pointers. While debugging, if you are inspecting abs_path while in parse it may very well be right. Remember that main will use abs_path, so you need to inspect it there too, when you return fr …

symbol is not submitted with the form because the name attribute needs to be defined on the select element. name is not a valid attribute for <option> elements, and the HTML will give errors if valida …

All things being equal, the only place that server returns a 505 is the parse function. If this parse function reaches for(int i=0;i<strlen(line);i++), it will always return a 505. Howzat? Assuming a …

server should return 505 in exactly one place, from the parse function http version check. That means that strcmp(HTTP_version, "HTTP/1.1") does not return 0. That means that HTTP_version is not "HTTP …

First suggest you send a request to server from browser or curl. You will discover that server seg faults. (That's what this \ expected output, not an exit code of 0 feedback from check50 indicates). …

So server returns a 404 error at line 209, before it executes lookup. See the link mentioned in the comment for hints on testing. NB this is not a duplicate of the referenced call. … That was a bug in lookup. This is a bug in parse. …

There's a bug in lookup. From the man page atoi() does not detect errors. This line int k = atoi(ext); is wrong. ext is going to be string data, that would be an error. So k could be anything. …

The problem isn't lookup. The problem is portfolio. There are exactly two keys in the portfolio dictionary, "current_price" and "holding_total". …

Since the quote spec calls for an element named "symbol", and this if not request.form.get("stock"): is apparently working, it looks like the element is not named properly in the html. FYI to change " …

Each dict in portfolio contains 3 keys as returned from the execute. There is no key current_price, so the html does not render anything for that column. If the key gets created in the for loop in ind …

The browser is very forgiving, what's one byte more or less? check50, on the other hand, is very precise. There is an extra byte in your content (and length) because of this usage: while (!feof(file)) …